We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For example take these two structures:
struct Section { struct Item { ... } var items: [Section.Item] } struct SomeOtherTypeWithNestedItemStruct { struct Item { ... } var items: [SomeOtherTypeWithNestedItemStruct.Item] }
If you later use the two Item structs as types for nbNavigationDestination they will override each other's builders and linking will fail:
Item
nbNavigationDestination
NBNavigationStack(path: $somePathBinding) { SomeView() .nbNavigationDestination(for: Section.Item.self, destination: { item in SomeItemView(item: item) }) .nbNavigationDestination(for: SomeOtherTypeWithNestedItemStruct.Item.self) { item in AnotherItemView(item: item) } }
The text was updated successfully, but these errors were encountered:
Maybe try builders[String(reflecting: T.self)] instead of builders["\(T.self)"] to store those builders...
builders[String(reflecting: T.self)]
builders["\(T.self)"]
Sorry, something went wrong.
Uses a fully qualified type identifier as key (#3)
f0ddc7e
Thanks to @zeusent.
Thanks for finding this issue @zeusent, and for the suggested change. It looks like the best approach, I'll make the necessary changes...
Released in v0.1.2
No branches or pull requests
For example take these two structures:
If you later use the two
Item
structs as types fornbNavigationDestination
they will override each other's builders and linking will fail:The text was updated successfully, but these errors were encountered: