Skip to content

Conversation

@einarmo
Copy link
Contributor

@einarmo einarmo commented Nov 11, 2025

This is a relatively simple implementation of this. Let users list dependent nodesets with import paths, like we allow for events. When actually generating the types, we store this as a map from namespace to import path, and during loading we just get the namespace of the type being loaded.

This only really works for nodeset2 files, but since there exists a workaround, this isn't critical. We can improve on this in the future.

With the codegen tests we can actually test stuff like this, which is quite nice.

This should fix #159.

@einarmo einarmo force-pushed the types-codegen-dependent-nodesets branch from 346eb7a to 0a5efb0 Compare November 11, 2025 14:00
This is a relatively simple implementation of this. Let users list
dependent nodesets with import paths, like we allow for events. When
actually generating the types, we store this as a map from namespace to
import path, and during loading we just get the namespace of the type
being loaded.

This only really works for nodeset2 files, but since there exists a
workaround, this isn't critical. We can improve on this in the future.

With the codegen tests we can actually test stuff like this, which is
quite nice.
@einarmo einarmo force-pushed the types-codegen-dependent-nodesets branch from 0a5efb0 to 3f907ff Compare December 3, 2025 09:05
@einarmo einarmo merged commit 12836bc into master Dec 3, 2025
6 checks passed
@einarmo einarmo deleted the types-codegen-dependent-nodesets branch December 3, 2025 09:08
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.

Codegen: respecting external types for type generation

3 participants