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

Default to correct use of the configuration file #116

Open
vigji opened this issue Feb 8, 2021 · 2 comments
Open

Default to correct use of the configuration file #116

vigji opened this issue Feb 8, 2021 · 2 comments
Labels
Refactor Improve source code readability, reusability or structure

Comments

@vigji
Copy link
Member

vigji commented Feb 8, 2021

This will probably be solved in the testing branch, but
sashimi

from the terminal should just give the execution of whatever is set to be in the configuration, and should not require the additional inputs

sashimi --scanning ni

as is currently happening.

@diegoasua
Copy link
Member

diegoasua commented Feb 9, 2021

After we have merged #112 and #92 there will be a chance for a PR completely focused on command line entries, config file and thereof. Understandably, this sort of entry right now can be a source of annoyance. However, we must proceed in order. This will be addressed, alas, now it is not the time yet

@diegoasua
Copy link
Member

diegoasua commented Feb 20, 2021

@vigji is there something around the config file that we want to modify in the current entry status? I think the issue you were pointing to at the beginning was branch-specific . The only optional entry now is --scopeless (correct me if I am wrong)

@diegoasua diegoasua added the Refactor Improve source code readability, reusability or structure label Feb 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Refactor Improve source code readability, reusability or structure
Projects
None yet
Development

No branches or pull requests

2 participants