Add ability to ignore enum cases with associated values #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add ability to ignore enum cases with associated values
♻️ Current situation & Problem
Currently, the TypeInformation framework will reject parsing any enums which contain enum cases with associated values.
This is e.g. a problem in the gRPC exporter, where every enum has a fallback case to support parsing unknown enum values.
💡 Proposed solution
This PR adds the ability to ignore enum cases with associated values instead of rejecting the enum completely. In our case this is fine, as the
UNRECOGNIZED
case shouldn't be handled anyway. The new option allows to easily add support for parsing those enum cases.⚙️ Release Notes
➕ Additional Information
Related PRs
Testing
Additional testing was added.
Reviewer Nudging
--
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: