[9.2 forward port] Add entity to the top level namespaces in which it's being used (#2556) #2557
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
…tic#2556) Add entity to the top level namespace of which it's used in sub-types. For example, we want user.target.entity fields to be present. user.entity itself is a user type, so entity must be reused on the user type. This also removes custom generator code which was being used to workaround the fact that this wasn't true before.
|
Documentation changes preview: https://docs-v3-preview.elastic.dev/elastic/ecs/pull/2557/reference/ |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
🔍 Preview links for changed docs |
kgeller
approved these changes
Oct 24, 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.
Forward port #2556 to 9.2
Add entity to the top level namespace of which it's used in sub-types.
For example, we want user.target.entity fields to be present. user.entity itself is a user type, so entity must be reused on the user type.
This also removes custom generator code which was being used to workaround the fact that this wasn't true before.