-
-
Notifications
You must be signed in to change notification settings - Fork 398
[skip-changelog] Add remediation path when tool is not available for an OS #2092
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
[skip-changelog] Add remediation path when tool is not available for an OS #2092
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #2092 +/- ##
==========================================
- Coverage 36.43% 36.43% -0.01%
==========================================
Files 229 229
Lines 19586 19587 +1
==========================================
Hits 7137 7137
- Misses 11611 11612 +1
Partials 838 838
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
bccf0c2
to
83554ba
Compare
83554ba
to
c7aad0c
Compare
c7aad0c
to
11792ed
Compare
return fmt.Errorf(tr("no compatible version of %s tools found for the current os, try contacting %s"), | ||
toolRelease.Tool.Name, toolRelease.Tool.Package.Email) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This string can not be correctly translated, you must replace unindexed %s
with %[1]s
and %[2]s
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Modified here: #2099
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
Code enhancement
What is the current behavior?
No instructions are provided when a tool download/install fails because it is not available for the OS in use.
What is the new behavior?
The error message has been enhanced by adding the
email
field of the package that provides the tool.Does this PR introduce a breaking change, and is titled accordingly?
No