fix: generate enum entries and constructors in JVM proxies - #28
Merged
Conversation
Parse enum entries from PSI body children and reconstruct constructor properties so jvmProxies can use Enum.entries without IndexOutOfBounds. Fixes #24
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
declarations) sojvmProxiesalways emit the actual constantsval code: Int, multi-param, string literals) instead of dropping themEnumTestcoverage (Color,Status,HttpStatus)Fixes #24
Type
fix
Test plan
:plugin-build:nna:test—PsiSourceParserEnumTest,FfmProxyGeneratorEnumTest:examples:calculator:generateKneNativeBridges—Operation/Color/Status/HttpStatusproxies contain entries (and constructor values):examples:calculator:jvmTest --tests com.example.calculator.EnumTest— 14 tests, including native ordinal round-trip