feat: emit per-variable field initializers in field declarations#145
Merged
sinha108 merged 1 commit intoJun 5, 2026
Merged
Conversation
sinha108
approved these changes
Jun 5, 2026
Merged
9 tasks
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
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.
Added a
variable_initializersfield to theFieldentity that records each declared variable's field expression as source text.Motivation and Context
Field initializers were not included in the old model, so constant values were unrecoverable by consumers, even though JavaParser already exposes them. I added a new field which maps each variable name to its initializer expression, and left the expression text unprocessed so interpretation can be done maximally by downstream consumers.
How Has This Been Tested?
There's a new test case in the
SymbolTableTestclass which covers various types of field declarations.Breaking Changes
There should be no breaking changes. The changes are purely additive.
Types of changes
Checklist
Additional context
I bumped the version to 2.3.8. I also used a
LinkedHashMapto preserve insertion order, so the initializers should serialize in declaration order deterministically.