Skip to content

Implement DerivedTypeMeta to store meta information for derived types#235

Merged
Bergmann89 merged 1 commit intomasterfrom
issue-234
Feb 7, 2026
Merged

Implement DerivedTypeMeta to store meta information for derived types#235
Bergmann89 merged 1 commit intomasterfrom
issue-234

Conversation

@Bergmann89
Copy link
Owner

Like GroupMeta, DynamicMeta may hold derived types with the same name (from different schemas), but in difference to GroupMeta, it does not provide meta information like the display_name, so we can not resolve potential naming conflicts as we do it for elements in GroupMeta. This commit implements DerivedTypeMeta which is stored in DynamicMeta to keep track of the derived types and it's meta information. It also resolves the issue with the naming conflicts for derived types by using setting a suitable display_name for conflicting names.

Related to #234

@Bergmann89 Bergmann89 force-pushed the issue-234 branch 2 times, most recently from 9657b4b to e5a8875 Compare February 7, 2026 22:20
Like `GroupMeta`, `DynamicMeta` may hold derived types with the same
name (from different schemas), but in difference to `GroupMeta`, it does
not provide meta information like the `display_name`, so we can not resolve
potential naming conflicts as we do it for elements in `GroupMeta`. This
commit implements `DerivedTypeMeta` which is stored in `DynamicMeta` to
keep track of the derived types and its meta information. It also resolves
the issue with the naming conflicts for derived types by using setting
a suitable `display_name` for conflicting names.
@Bergmann89 Bergmann89 merged commit 08aa3ce into master Feb 7, 2026
2 checks passed
@Bergmann89 Bergmann89 deleted the issue-234 branch February 7, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant