Skip to content

Conversation

@emesare
Copy link
Member

@emesare emesare commented Dec 11, 2025

This helps with documentation, giving a single module for those working with types to find related APIs

Also split out enumeration and structure APIs into their own file, since they have their own backing data separate from Type.

This does not actually break any plugins since these modules that were moved and not re-exported are not used as of yet.

The APIs which are being used have re-exports that allow existing code to correctly import.

@emesare emesare added the Component: Rust API Issue needs changes to the Rust API label Dec 11, 2025
@emesare emesare added this to the Jotunheim milestone Dec 11, 2025
@emesare emesare force-pushed the test_rust_types_mod branch from cf8379e to ae3e75b Compare December 13, 2025 20:30
This helps with documentation, giving a single module for those working with types to find related APIs

Also split out enumeration and structure APIs into their own file, since they have their own backing data separate from `Type`.
@emesare
Copy link
Member Author

emesare commented Dec 13, 2025

One unfortunate thing is we keep QualifiedName in the types module, I think we should move it out and re-export it within types module with a deprecation notice.

This is used in more places than types, so its best we keep it separate.
- Added some unit tests
- Improved documentation
- Made `QualifiedName::new` and `QualifiedName::new_with_separator` generic over `Into<String>`
@emesare emesare merged commit 8e409a0 into dev Dec 16, 2025
9 of 10 checks passed
@emesare emesare self-assigned this Dec 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component: Rust API Issue needs changes to the Rust API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants