Skip to content
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

Revert location of config yml file until a default/override config system is in place #205

Merged
merged 2 commits into from
Nov 1, 2024

Conversation

adraismawur
Copy link
Collaborator

@adraismawur adraismawur commented Nov 1, 2024

This moves the config.yml back into the big_scape folder. This makes it harder for users to find but should be temporary until we get a better system.

The way we are currently using the configuration is a bit rigid - you either supply it with all of the values that the config as or you don't provide one. We should move to a default/override structure where A user can provide a partial set of configuration items which will be overridden, and the rest are inferred from default.

This way we can supply a default_config.yml with a bunch of explanations in the root of the directory, and we can keep a default config with all default values.

This also adds a few edits to the pyproject.toml which I think make it more robust in terms of pathing. Not sure. It seemed to help 🤷‍♂️

@adraismawur adraismawur self-assigned this Nov 1, 2024
Copy link
Collaborator

@CatarinaCarolina CatarinaCarolina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems to work!

@adraismawur adraismawur merged commit ec88659 into dev Nov 1, 2024
4 checks passed
@adraismawur adraismawur deleted the hotfix/fix-config-pip-install branch November 7, 2024 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants