-
Notifications
You must be signed in to change notification settings - Fork 32
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
Towards semi-automated path generation #178
Conversation
Given that we have a well defined structure, we should ideally be able to generate all paths automatically. The information is present, we just need to figure out how to use it.
That is very cool. (Caution. I'm the implementer/maintainer of You might also look at the GraphQL support that is provided by the I've attached a screen shot. And, here are two bash scripts that show how I generated the
The above requires the latest version of
You can learn more about the GraphQL support provide by |
Woah! That's really nice! It's on my TODO list to learn about GraphQL and see how we can leverage generateDS's support for it to make it easier to inspect (but also hopefully create?) NeuroML objects/models. After seeing your screenshot, i think I need to bump it up the list :) Thanks again for all your help. |
Given that the schema is well defined, we should, in some way be able to automate the generation of paths or provide "hints" towards what paths should be. This is sort of a first step to provide the user with more information about relative paths and hierarchies of the schema, without them having to click through the docs to figure it all out. It adds:
example usage:
For paths, it adds a convenience function that provides hints on the relative paths from one place in the standard hierarchy to another:
A lot more "intelligence" can be baked into these bits to fill up lots of common bits for the user.