Move hints to their own place, with API and unicorns #3495
Merged
+336
−127
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
happz
added
code | style
happz
requested review from
frantisekz,
psss,
lukaszachy,
thrix,
janhavlin and
martinhoyer
as code owners
happz
force-pushed
the
hints-everywhere
branch
from
e1a399b to
7e5490e
Compare
happz
added
ci | full test
|
Adding |
happz
force-pushed
the
hints-everywhere
branch
5 times, most recently
from
176d9dd to
d54ed6d
Compare
happz
force-pushed
the
hints-everywhere
branch
3 times, most recently
from
a08c302 to
1d6b965
Compare
happz
removed
the
status | blocked
happz
force-pushed
the
hints-everywhere
branch
2 times, most recently
from
ae6f753 to
af70e2e
Compare
therazix
approved these changes
Feb 20, 2025
therazix
reviewed
Feb 20, 2025
happz
force-pushed
the
hints-everywhere
branch
from
af70e2e to
3ae00ab
Compare
happz
force-pushed
the
hints-everywhere
branch
from
3ae00ab to
4c41d92
Compare
happz
added
the
status | blocking other work
I wanted to change a couple of things about "hints" tmt shows to users when when a package is missing and functionality is limited: * Static, stored in a single function. That made them detached from their origin, and 3rd party plugins would have no chance to add their own hints. * A bit confined text of hints did not cover all possible venues. PyPI installation was ignored by some, other hints spoke just about using `pip install`. * Hints are interesting and useful, but visible only when error strikes. The patch turns the function into a "registry", a simple dictionary storing them. Plugins and tmt code in general can "register" their hints, and a nice tools are available for showing them. Hints wow have IDs, and there are dedicated IDs for step-specific (``report``, ...) and plugin-specific (``report/foo``) hints, allowing tmt core to print them when step or plugins crashes on import. Plugin-specific hints are now rendered both in their CLI and HTML documentation. In the future, I would like to provide hints not just as "a package foo is missing, install it" guide, but also explaining various errors and issues tmt would report, e.g. pairing them with exceptions, "To learn more, run `tmt about E1234`".
lukaszachy
force-pushed
the
hints-everywhere
branch
from
4c41d92 to
bffe2c3
Compare
lukaszachy
approved these changes
Feb 26, 2025
happz
added
the
status | ready for merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted to change a couple of things about "hints" tmt shows to users when when a package is missing and functionality is limited:
pip install.The patch turns the function into a "registry", a simple dictionary storing them. Plugins and tmt code in general can "register" their hints, and a nice tools are available for showing them.
Hints wow have IDs, and there are dedicated IDs for step-specific (
report, ...) and plugin-specific (report/foo) hints, allowing tmt core to print them when step or plugins crashes on import.Plugin-specific hints are now rendered both in their CLI and HTML documentation.
In the future, I would like to provide hints not just as "a package foo is missing, install it" guide, but also explaining various errors and issues tmt would report, e.g. pairing them with exceptions, "To learn more, run
tmt about E1234".Pull Request Checklist
tmt about, together with listing all discovered plugins it should give me enough tools to test the features