jmix-create-enum: state that extra constant state is invisible to the metamodel - #132
Merged
Merged
Conversation
knstvk
marked this pull request as ready for review
September 16, 2026 13:07
knstvk
pushed a commit
that referenced
this pull request
Sep 16, 2026
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
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.
Fixes #130.
Drafted from a field report while the problem was fresh, by the agent that hit it. It is unreviewed: treat the wording as a starting point, not a proposal to merge as-is.
Change
Adds a note under the Enum Template saying that an
EnumClassconstant may carry constructor arguments and accessors beyond the stable id, that they are invisible to the metamodel (an enum is not a@JmixEntity; the enumeration datatype reads onlygetEnumConstants()andgetId()) and therefore owe no message key, and that only the stable id is ever persisted.