You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In utils.rs, the find_enum_by_name and find_enum_by_name_in_message functions assume the enum is the last part of the full enum path and that the rest of the enum path is the package. It does not consider that the enum may be nested within another message. This results in the plugin searching for the enum .some.package.TestMessage.TestEnum in the "package" .some.package.TestMessage which is not actually a package, and thus it does not find it.
This is similar in effect to #30, but a little different in how the bug manifests.
The text was updated successfully, but these errors were encountered:
👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-1458). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.
In utils.rs, the find_enum_by_name and find_enum_by_name_in_message functions assume the enum is the last part of the full enum path and that the rest of the enum path is the package. It does not consider that the enum may be nested within another message. This results in the plugin searching for the enum .some.package.TestMessage.TestEnum in the "package" .some.package.TestMessage which is not actually a package, and thus it does not find it.
This is similar in effect to #30, but a little different in how the bug manifests.
The text was updated successfully, but these errors were encountered: