Suppress false assumed-(required) handling for primitive entity IDs and merge compiler dependency updates#301
Draft
Copilot wants to merge 16 commits into
Draft
Suppress false assumed-(required) handling for primitive entity IDs and merge compiler dependency updates#301Copilot wants to merge 16 commits into
(required) handling for primitive entity IDs and merge compiler dependency updates#301Copilot wants to merge 16 commits into
Conversation
Agent-Logs-Url: https://github.com/SpineEventEngine/validation/sessions/c0c59d00-5e83-41d0-8488-c2618a6ea31a Co-authored-by: alexander-yevsyukov <3116444+alexander-yevsyukov@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix false warning for assumed required ID of entity state
Suppress false assumed-May 13, 2026
(required) handling for primitive entity IDs
... because we don't longer support it.
Add a KDoc reference to #305 on the `prohibit an entry with empty string` test so the rationale for it being `@Disabled` is discoverable from the source.
Collaborator
…o copilot/fix-false-warning-for-required-id # Conflicts: # java/src/main/kotlin/io/spine/tools/validation/java/generate/option/RequiredGenerator.kt Co-authored-by: alexander-yevsyukov <3116444+alexander-yevsyukov@users.noreply.github.com>
Author
|
Merged PR #306 into this branch and resolved the single conflict in Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
Suppress false assumed-
Suppress false assumed-May 20, 2026
(required) handling for primitive entity IDs(required) handling for primitive entity IDs and merge compiler dependency updates
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.
Entity state IDs are implicitly treated as
(required), but that assumption was leaking onto primitive IDs such asint32, producing misleading warnings and incorrect validation behavior. This change narrows implicit required handling to field types that actually support(required).This branch also now includes the merged changes from the dependency-update work on
bump-compilers, so the resulting PR contains both the primitive-ID fix and the latest compiler/dependency refresh.Behavior change
(required)validation for implicitly required IDs whose field type does not support the option.Regression coverage
int32ID.Merged dependency update scope
RequiredGeneratorchanges introduced by the dependency update.Why this matters
(required)semantics.(required)when the field was only inferred by convention.Example covered by the change:
Before this change, the first field could be treated as implicitly
(required)despiteint32not supporting that option. With this update, primitive IDs like the above are ignored by required-field generation.