Can no longer specify paths to custom schemas
See original GitHub issuePreviously, you could use config
to pass the path of a .json
config file to define custom entities. This no longer works, because config
takes a list of names and not paths. Passing in a path will not work as the path of pybids configs will be appended to it.
This might be a problem for some users, and we could potentially add this functionality back in.
@effigies this affects fitlins. can you live without this feature? it looks like you pass a custom set of entities only when using BIDSLayout
for outputting new paths, in which case you could potentially just use a basic grabbit Layout
which still accepts full paths in its API.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Custom schemas path won't work · Issue #23 · mattyod/matic
Any schemas path other than "schemas" will still create the target output folder specified, but will NOT render the respective .html output ...
Read more >Custom schemas - dbt Developer Hub
Use the schema configuration key to specify a custom schema for a model. As with any configuration, you can either:.
Read more >DBT custom schema using folder structure - Stack Overflow
So, the command is basically removing the first and last position of the list (project name & model name) leaving only the remaining...
Read more >Learn how AWS Glue crawler detects the schema
When you define an AWS Glue crawler, you can choose one or more custom classifiers that evaluate the format of your data to...
Read more >Documentation: 15: 5.9. Schemas - PostgreSQL
To put our new schema in the path, we use: SET search_path TO myschema,public; (We omit the $user here because we have no...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Let’s go with the module-level
add_config()
approach; I think it makes sense to be explicit about something like this, and the pybids codebase is already pretty bloated with type-checking and validation. Want to open a PR?That would work for me.
The alternative is to allow
config
to take either keywords (bids
orderivatives
) or paths. If an elemnt of the list is not one of the reserved keywords, it can be assumed to be a full path. I suppose that makes the API a bit more complex, but it seems like a reasonable amount.As an aside, I don’t think its a big deal to have to call
add_derivatives
if you want more control as to how derivatives are added (whereasderivatives=
is really just a “short cut” for a default configuration for derivatives).