You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v0.16 datalad provides a `register_config()` helper for extensions
to inject their own configuration into the central registry.
This changeset replaces the previous custom implementation with this
standard approach. It has not consequences re user behavior.
An additional benefit is that this configuration is now also
user-accessible, including a basic documentation:
```py
>>> import datalad_container
>>> from datalad.api import configuration
>>> configuration('dump', 'datalad.containers.location')
datalad.containers.location=.datalad/environments
[{'action': 'dump_configuration',
'refds': '/home/mih/hacking/datalad/container',
'name': 'datalad.containers.location',
'value': '.datalad/environments',
'purpose': 'Container location',
'description': 'path within the dataset where to store containers',
'value_type': constraint:str,
'path': '/home/mih/hacking/datalad/container',
'status': 'ok'}]
```
Closesdatalad#239
datalad-container/datalad_container/containers_add.py
Line 235 in c505e52
This would make it possible to discontinue the approach in
definitions.py
register_config
was introduced with datalad v0.16The text was updated successfully, but these errors were encountered: