Skip to content
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

Open
SeeThruHead opened this issue Apr 5, 2016 · 4 comments
Open

Nested namespace #38

SeeThruHead opened this issue Apr 5, 2016 · 4 comments

Comments

@SeeThruHead
Copy link

devcard.ns('sub-namespace') ? to create a nested namespace?

I can take a look at this if you think it's worthwhile.

@glenjamin
Copy link
Owner

Seems like a good idea

API-wise how about these options?

devboard.ns(a, b, c)
devboard.ns("a/b/c")

@glenjamin
Copy link
Owner

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

@SeeThruHead
Copy link
Author

I hadn't thought about non-leaf but you could put the links up top, and any cards below, to keep it simple.
As for api it could just do either.

EDIT: I think it should definitely contain sub-links, more important than non-leaf cards i think

@glenjamin
Copy link
Owner

Ok, let's go for

  • multi-arg API
  • can have cards at every level
  • tree view on the root
  • same tree view of children on namespaces that have them

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

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

No branches or pull requests

2 participants