-
Notifications
You must be signed in to change notification settings - Fork 3
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
Decide whether to show included spec fields #3
Comments
Thanks for reporting the issue. What are the steps leading to this error ? As a side note, you can now |
error:
error:
That's just a path error. It should be But when I fix that:
error:
|
@bendichter the init_sphinx_extension_doc script needs to be updated to not copy the sources that are now in nwb-docutils but rather to use nwb-docutils directly. |
I just push some fixes to nwb-docutils that account for the fact script are not anymore located in the There is no intermediate errors anymore. Here are the steps so far: Install from source:
Then:
The following error is reported:
|
@oruebel A new version of nwb-docutils was just published on pypi, the new version doesn't copy the source of utils into the extension. |
This commit fixes the error reported below and ensure the complete schema documentation including both the core and the extension schema is generated. ``` Traceback (most recent call last): File "/home/jcfr/Projects/pynwb/src/pynwb/form/spec/namespace.py", line 379, in load_namespaces inc_ns = self.get_namespace(s['namespace']) File "/home/jcfr/Projects/pynwb/src/pynwb/form/utils.py", line 348, in func_call return func(self, **parsed['args']) File "/home/jcfr/Projects/pynwb/src/pynwb/form/spec/namespace.py", line 240, in get_namespace raise KeyError("'%s' not a namespace" % name) KeyError: "'core' not a namespace" ``` See #3 Co-authored-by: Andrew Tritt <[email protected]>
In the process we understood the following: (1) Addressing the error removing the reference to
|
In both cases (1) and (2) the document generator needs to be fixed because the docs won't link back properly to the docs if you remove the 'core' from the schema. At least for now, I think we can simplify this problem by focusing on what is needed for the 'core' docs from the nwb-schema repo and the extension docs from the new nwb-extensions repo. If we want to render only the parts that are new to the extension then a possible solution would be to:
Note, there is also an additional variant to this, in that we can set |
I like the idea of setting I have 2 example extensions up, each with documentation rendered, including the entire core. Right now it's difficult to know which classes belong to the extension, so I think limiting what is shown to new extension classes would be very useful. |
make apidoc
gives the following error:The text was updated successfully, but these errors were encountered: