You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Each folder in `cli` should correspond to a command group. The name of the folder should be the name of the command group. Ex: `task` for codegen task commands.
11
+
- The command group folder should have a file called `commands.py` where the CLI group (i.e. function decorated with `@click.group()`) and CLI commands are defined (i.e. functions decorated with ex: `@task.command()`) and if necessary a folder called `utils` (or a single `utils.py`) that holds any additional files with helpers/utilities that are specific to the command group.
12
+
- Store utils specific to a CLI command group within its folder.
13
+
- Store utils that can be shared across command groups in an appropriate file in cli/utils. If none exists, create a new appropriately named one!
- Each folder in `cli` should correspond to a command group. The name of the folder should be the name of the command group. Ex: `task` for codegen task commands.
4
-
- The command group folder should have a file called `commands.py` where the CLI group (i.e. function decorated with `@click.group()`) and CLI commands are defined (i.e. functions decorated with ex: `@task.command()`) and if necessary a folder called `utils` (or a single `utils.py`) that holds any additional files with helpers/utilities that are specific to the command group.
5
-
- Store utils specific to a CLI command group within its folder.
6
-
- Store utils that can be shared across command groups in an appropriate file in cli/utils. If none exists, create a new appropriately named one!
1
+
# Codegen GS CLI
2
+
This module to be moved out into `src/code_generation`
0 commit comments