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

CLI-defined input and output paths #25

Open
hyperrealgopher opened this issue Jun 15, 2021 · 1 comment
Open

CLI-defined input and output paths #25

hyperrealgopher opened this issue Jun 15, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@hyperrealgopher
Copy link
Collaborator

hyperrealgopher commented Jun 15, 2021

Ignoring the path variable from the CLI and just using the INI to get the output directory and input directory.

Need to either drop CLI support for defining the input and output path and compeltely rely on the ini file, or completely implement support for the CLi args.

This may also go hand-in-hand with adding a config abstraction, because then the config abstraction could have its output/input entries changed early on before it's passed around. Related: #20

@hyperrealgopher
Copy link
Collaborator Author

Dropped CLI support for output and source directories. Need to reimplement.

@hyperrealgopher hyperrealgopher mentioned this issue Aug 19, 2021
2 tasks
@hyperrealgopher hyperrealgopher added the enhancement New feature or request label Aug 23, 2021
@hyperrealgopher hyperrealgopher changed the title bug: CLI-defined input and output paths ignored in many places CLI-defined input and output paths Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant