Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enum not found in nested proto field #38

Closed
rkrishnan2012 opened this issue Nov 7, 2023 · 1 comment
Closed

Enum not found in nested proto field #38

rkrishnan2012 opened this issue Nov 7, 2023 · 1 comment
Labels
smartbear-supported Issues with this label have been added to the Pactflow team's Jira backlog

Comments

@rkrishnan2012
Copy link
Contributor

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.

@mefellows mefellows added the smartbear-supported Issues with this label have been added to the Pactflow team's Jira backlog label Nov 7, 2023
Copy link

github-actions bot commented Nov 7, 2023

👋 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.

See our documentation for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
smartbear-supported Issues with this label have been added to the Pactflow team's Jira backlog
Projects
None yet
Development

No branches or pull requests

2 participants