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

Add README #1

Closed
pdvyas opened this issue Jul 11, 2014 · 0 comments
Closed

Add README #1

pdvyas opened this issue Jul 11, 2014 · 0 comments

Comments

@pdvyas
Copy link
Contributor

pdvyas commented Jul 11, 2014

No description provided.

@pdvyas pdvyas closed this as completed in 15e8568 Jul 16, 2014
rmehta pushed a commit that referenced this issue Jul 4, 2016
gavindsouza added a commit that referenced this issue Jul 27, 2022
The implementations so far were hacks that worked for the most used
commands but broken down when challenged or expected to maintain
documented usages [eg: custom app commands].

The current implementation consists of a two step approach:
1. figure out command name that user is trying to execute
2. pass the directive to the app (bench, frappe or other) that consists of the cmd

---

For tackling #1, get_cmd_from_sysargv contains exhaustive rules that
cover all (that i know and ive come across) combinations of valid
frappe commands.

For problem #2, a simple check in click's Group object does the trick.

Tested with possible known commands with combinations of context flags
and params, with bench, frappe & external app's commands
@saleh6449 saleh6449 mentioned this issue Apr 4, 2023
1 task
@bonsaihorn bonsaihorn mentioned this issue May 18, 2024
2 tasks
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

No branches or pull requests

1 participant