AI Tools: annotation-based entity exclusion for Data Load tools (5637) - #5672
Open
Flaurite wants to merge 2 commits into
Open
Conversation
Flaurite
changed the title
knstvk
approved these changes
Sep 10, 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.
Changes
Added new annotation to AI Tools -
@ExcludeFromAi.This annotation marks an entity or attribute as off-limits to the AI: it's dropped from the domain-model index, so it never appears in discovery and any generated query referencing it is rejected.
This check has absolute priority in the introspector, and cannot be overriden by application properties.
@ExcludeFromAican be inherited by subclasses. So a subclass of an excluded entity can't silently re-expose the data.