Fix #11127: enforce non-null keys for InputLocation lookups and document behavior (master) #11129
Conversation
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
…complete Javadoc on master\n\n- modello templates: add Objects.requireNonNull(key, "key") in InputLocation.getLocation(Object)\n- modello templates: document non-null key requirement in InputLocationTracker and method Javadoc\n- ensure generated model code across modules reflects the contract\n\nFormatting: spotless applied. Full build to be run in CI.
cstamas
approved these changes
Sep 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This ports #11128 to master.
Formatting via Spotless; verified local generation and targeted module build. Full CI will validate the entire reactor.
After merge, we can consider back/forward-port alignment as needed.
Pull Request opened by Augment Code with guidance from the PR author