You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposal is to add a namespace_path attribute that would accept a syn::Path. The generated type would then be wrapped in the specified namespace (with :: indicating levels of the namespace).
This would give a way to handle name collisions, addressing #16
Not sure what the best name for the attrs should be. It also doesn't follow Typescripts convention of using CamelCase to name namespaces, but a compromise needs to be made somewhere...
The text was updated successfully, but these errors were encountered:
The proposal is to add a
namespace_path
attribute that would accept asyn::Path
. The generated type would then be wrapped in the specified namespace (with::
indicating levels of the namespace).For example:
would produce
There should be a corresponding option to use a path as a namespace for a declared type. For example
would produce
This would give a way to handle name collisions, addressing #16
Not sure what the best name for the attrs should be. It also doesn't follow Typescripts convention of using CamelCase to name namespaces, but a compromise needs to be made somewhere...
The text was updated successfully, but these errors were encountered: