Handle base fields imported from nested ECS definitions in a more generic way #779
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.
More future-proof implementation of #777.
Previous implementations considers
base
andtracing
the only groups that cancontain top-level fields. Implementation on this change checks field by field to see
if they contain base fields.
It also handles the case of having groups with both nested and top-level fields, something
that doesn't happen now, but just in case, to don't lose definitions if it happens at some
moment.