-
Notifications
You must be signed in to change notification settings - Fork 27
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
default_name unused #50
Comments
This has likely been masked by the fact that most data types require a |
Fixed by #91 |
@rly The PR goes some way to address this issue, but the fix we just merged is just for classes that are constructed dynamically by get_class in pynwb, and does not apply to other classes like |
This issue requires changing Container and docval to work with "default_name". This is not high priority. Please reopen if it is a priority. |
I searched through the hdmf and pynwb source code and could not see any place where
default_name
of a spec is actually used besides when it is stored. In fact, I can change thedefault_name
on a data type likePosition
innwb.behavior.yaml
and there is no effect:The default name is set as the class name when no
name
argument is specified.Environment
Please describe your environment according to the following bullet points.
The text was updated successfully, but these errors were encountered: