-
Notifications
You must be signed in to change notification settings - Fork 979
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
Support named log groups #1477
Comments
Thanks for the suggestion - having a hierarchy here seems like it might be useful, indeed. However, there are a lot of considerations around page rendering and performance that we would need to think through. I'm going to put this on the backlog, but this isn't something that we have planned to work on in the very near future. Thanks again! |
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
Still interesting. |
Describe the enhancement
Currently, it is possible to wrap logs in collapsible groups through
::group::
and::endgroup::
. The former accepts an optional string, which is used as the title of the collapsible header. However, the endgroup does not support any additional argument. As a result, it is not possible to uniquely identify the matching start and end statements, thus, preventing nesting, hierarchical view, etc.The implementation of this feature in other services allows using a keyword to match open and close statements.
Code Snippet
Possible enhancement:
Additional information
Since composite actions can include other actions (up to 10 levels of hierarchy), log groups are likely to conflict. Keywords might be implicitly used for enhancing the current UI.
Refs: #802 #1272 #1279 #1404
/cc @thboop @andreineculau @pbartolome
The text was updated successfully, but these errors were encountered: