Fixit CLI about fixit HOT 7 CLOSED

Having a single CLI command is a good idea. We already do that for LibCST.
To keep it simple, the command should be named as fixit
and users can provide different sub-command, e.g.

• fixit run_rules
• fixit apply_fix

Why do you need both launch_cli and main rather than just a main?
Then the console-script can point to cli.main:main.

from fixit.

Your PRs are very welcome!

from fixit.

Your PRs are very welcome!

Thank you, Should I do in separate folder? i.e fixit/cli2/

from fixit.

Having a single CLI command is a good idea. We already do that for LibCST.
To keep it simple, the command should be named as fixit
and users can provide different sub-command, e.g.

• fixit run_rules
• fixit apply_fix

Why do you need both launch_cli and main rather than just a main?
Then the console-script can point to cli.main:main.

Yes, I can do that too. But, I want to parse arguments separately and TBH more modular. So this is one way I can think of.
Let me know if you have any other ideas.

from fixit.

Your PRs are very welcome!

Thank you, Should I do in separate folder? i.e fixit/cli2/

How should I make PRs? because I need to change some existing files in each small PR for each sub-command, which might cause conflict.

from fixit.

Your PRs are very welcome!

Thank you, Should I do in separate folder? i.e fixit/cli2/

How should I make PRs? because I need to change some existing files in each small PR for each sub-command, which might cause conflict.

I would just add a cli/main.py and modify other files to add them to the new CLI while keeping their existing CLI works for backward compatibility.
One or multiple PRs are both fine to me.

from fixit.

Thank you.

from fixit.