-
Notifications
You must be signed in to change notification settings - Fork 18
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 logic for key validation in report subcommand #201
Conversation
Signed-off-by: Subham Sarkar <subhamsarkar@DeepSource-C02DRL12ML7H.local>
LAE-7238 CLI: Raise an error if the `--key` parameter is not a valid language
A user was sending Prevent the user from sending a bad value as key, and give a much better error message in the CLI:
|
Signed-off-by: Subham Sarkar <subham@deepsource.io>
Signed-off-by: Subham Sarkar <subham@deepsource.io>
Signed-off-by: Subham Sarkar <subham@deepsource.io>
Signed-off-by: Subham Sarkar <subham@deepsource.io>
Signed-off-by: Subham Sarkar <subham@deepsource.io>
To make the tests pass, I think we have to update the DSN. @siddhant-deepsource Right? |
Its the issue with using the test coverage github action. Ref: https://discuss.deepsource.io/t/breaking-deepsource-test-coverage-github-action/507 |
Signed-off-by: Tushar Sadhwani <86737547+tushar-deepsource@users.noreply.github.com>
Signed-off-by: Tushar Sadhwani <86737547+tushar-deepsource@users.noreply.github.com>
CI is fixed now. |
Signed-off-by: Tushar Sadhwani <86737547+tushar-deepsource@users.noreply.github.com>
Signed-off-by: Subham Sarkar <subham@deepsource.io>
If the wrong value is passed to
--key
indeepsource report
, it would send it to the backend and return a cryptic error message.This ensures that you pass a supported language to
--key
.