Replace incorrect use of getIndex() in EnumValueDescriptor with getNumber() #226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
snazy
reviewed
Jul 14, 2022
core/src/test/java/org/projectnessie/cel/common/types/ProviderTest.java
Outdated
Show resolved
Hide resolved
snazy
approved these changes
Jul 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #225
getNumberrather thanordinalon the generated Java enum (which theEnumValueDescriptor'sgetIndexcorresponds tocel-goimplementation thatcel-javais based on usesgetNumbercel-javausegetNumberNote: the test update corrects the test to do the right thing, but it doesn't fail in the existing (incorrect) implementation because the test enum has
getNumber() == getIndex()for all values.