-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
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
Nested namespace #38
Comments
Seems like a good idea API-wise how about these options? devboard.ns(a, b, c)
devboard.ns("a/b/c") |
Would you expect to be able to put cards in non-leaf namespaces? I think this should be allowed Should the namespace page include links to sub namespaces, or should the tree view only be on the root list? Unsure about this one |
I hadn't thought about non-leaf but you could put the links up top, and any cards below, to keep it simple. EDIT: I think it should definitely contain sub-links, more important than non-leaf cards i think |
Ok, let's go for
Implementation-wise I reckon you could get away with using the JSON-encoded namespace path as the key for the catalog. URLs might be tricky |
devcard.ns('sub-namespace') ? to create a nested namespace?
I can take a look at this if you think it's worthwhile.
The text was updated successfully, but these errors were encountered: