-
Notifications
You must be signed in to change notification settings - Fork 17
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
💡 [Feature]: extend CLI command logs with full name and options passed #283
Comments
lets keep this on hold until this issue is resolved #295 |
lets not care about it. We may always document that we are using older version of CLI under the hood |
I would like to work on this problem |
All yours. |
…313) ## 🎯 Aim Adding the m365 prefix: The m365 prefix is now included before every CLI command, ensuring that the logged commands accurately reflect what is run in the terminal. Logging CLI command options: The PR also includes the functionality to log the options passed with each command, providing better transparency and guidance for developers who want to understand the equivalent terminal commands for SPFx Toolkit features. However, the functionality to set json as the default output for all commands was not implemented, as there are parts of the code that use other output formats, such as md (Markdown). Changing the default output to json globally could break those functionalities. ![image](https://github.com/user-attachments/assets/61a93e6a-712f-4122-82fb-f00ae3ce18b7) ## 📷 Result ![Captura de tela 2024-09-30 124116](https://github.com/user-attachments/assets/0dce5b35-2022-4e54-980a-4c318441282f) ![Captura de tela 2024-09-30 124152](https://github.com/user-attachments/assets/eb01d647-8580-4677-912a-ea6af1ae10d2) ## 🔗 Related issue Closes: #283
PR merged. |
…313) ## 🎯 Aim Adding the m365 prefix: The m365 prefix is now included before every CLI command, ensuring that the logged commands accurately reflect what is run in the terminal. Logging CLI command options: The PR also includes the functionality to log the options passed with each command, providing better transparency and guidance for developers who want to understand the equivalent terminal commands for SPFx Toolkit features. However, the functionality to set json as the default output for all commands was not implemented, as there are parts of the code that use other output formats, such as md (Markdown). Changing the default output to json globally could break those functionalities. ![image](https://github.com/user-attachments/assets/61a93e6a-712f-4122-82fb-f00ae3ce18b7) ## 📷 Result ![Captura de tela 2024-09-30 124116](https://github.com/user-attachments/assets/0dce5b35-2022-4e54-980a-4c318441282f) ![Captura de tela 2024-09-30 124152](https://github.com/user-attachments/assets/eb01d647-8580-4677-912a-ea6af1ae10d2) ## 🔗 Related issue Closes: #283
🎯 Aim of the feature
Currently the logs for CLI commands are quite short
we are missing the
m365
before every command and we do not print out the passed options that were used to run this command. This does not help as the actually idea behind this functionality was to provide guidance for developers what are the CLI commands that may use as equivalent to the SPFx Toolkit feature if they would rather use a terminal instead.We should fix it up.
In order to do that we should recheck the
tryExecuteCommand
method inhttps://github.com/pnp/vscode-viva/blob/main/src/services/CliCommandExecuter.ts
We should add:
m365
for every commandtext
. IMO it should be alwaysjson
and we could then remove passing it in all placesThe text was updated successfully, but these errors were encountered: