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

Configuration file should be taken as an argument #34

Open
mufeedvh opened this issue Jul 2, 2022 · 0 comments
Open

Configuration file should be taken as an argument #34

mufeedvh opened this issue Jul 2, 2022 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@mufeedvh
Copy link
Owner

mufeedvh commented Jul 2, 2022

Currently for convenience, a configuration file is generated on the first run and is always consumed from the same working directory as the binary is executed. This implementation was to make project separation easier but comes with an overlooked issue where the executable file could/should be placed outside of a project directory.

This is a tracking issue alongside #32 to implement override for every configuration functions.

@mufeedvh mufeedvh added the enhancement New feature or request label Jul 2, 2022
@mufeedvh mufeedvh added this to the v0.2.1 milestone Jul 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant