-
Notifications
You must be signed in to change notification settings - Fork 95
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
Support YAMLs for config files #1030
Comments
As long as any of these files will be read into identical python dictionaries, this should be a fairly lightweight change (for someone besides me to implement). The changes I see are:
As for yaml vs toml, I don't know enough to have a real opinion. For me various factors are:
|
maPCA should not be using any json, no. That said, json works better with Rica if it's ever needed. |
I meant |
Rica doesn't use the registry json at the moment. It uses the tsv files but that's only because I haven't had the chance to add more features. |
Summary
YAML is essentially just JSON with some nice formatting and comments allowed. We could have an if/else statement at the part where config files are read in that just switches which function is used to read in the contents.
Additional Detail
In the BIDS schema we chose to use YAMLs instead of JSONs because they're more readable and allow comments.
The Nipreps tools generally use TOMLs instead of JSONs for configuration files, so that might be worth considering as well.
The text was updated successfully, but these errors were encountered: