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
First step towards enabling others to use the package. Possible implementation would be creating a sub-folder in the data folder that's not synced to Git. This folder would have a params.json that's specific to the user. The original params.json would used as the default and copied when the user first runs.
The text was updated successfully, but these errors were encountered:
I suppose this isn't actually an issue if this were a distributed package. The actual concern here is for developers to be able to have a config file that doesn't get over-written when another developer syncs with git. Could just put the config file in a folder that doesn't sync and provide a link to download a template config file for anyone new to the project
Now each contributor can modify their own params.json without affecting the others. It may delete your current params.json file, but you can copy a template from data/default_params into /data. I've also added an error message that will tell the user this. If someone's ambitious, they could automate this.
First step towards enabling others to use the package. Possible implementation would be creating a sub-folder in the data folder that's not synced to Git. This folder would have a params.json that's specific to the user. The original params.json would used as the default and copied when the user first runs.
The text was updated successfully, but these errors were encountered: