Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Nested logging groups tree-view #1001

Open
aminya opened this issue Feb 14, 2022 · 1 comment
Open

Nested logging groups tree-view #1001

aminya opened this issue Feb 14, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@aminya
Copy link

aminya commented Feb 14, 2022

Describe the enhancement
Currently, if nested groups are created using startGroup and endGroup in the UI they are shown next to each other. The expectation is that the internal groups are hidden in the parent group.

For example, here the more detailed group show be hidden unless the parent group is expanded:
image

Code Snippet

startGroup("parent")

startGroup("child")
endGroup()

endGroup()

Additional information
@aminya aminya added the enhancement New feature or request label Feb 14, 2022
@oli-obk oli-obk mentioned this issue Dec 7, 2022
Closed
@SubaruArai SubaruArai mentioned this issue Aug 8, 2023
Merged
@zirkelc zirkelc mentioned this issue Oct 4, 2023
Merged
@chrissimon-au chrissimon-au mentioned this issue Nov 21, 2023
Closed
@eli-schwartz eli-schwartz mentioned this issue Aug 1, 2024
Merged
klaernie added a commit to klaernie/editorconfig-checker that referenced this issue Aug 16, 2024
@klaernie
feat(output): support output format github-actions (closes editorconf…
ee8085b 
…ig-checker#317)

Now one can request `--format github-actions` and get the errors
returned in a format that should be parsable by Github Actions.

I decided against implementing the grouping feature (so errors would be
additionally grouped per file), since nested groups are not yet
supported - actions/toolkit#1001
Doing so would then break the use cases where a linter collection
like mega-linter or super-linter use groups themselves (e.g. to group
errors by linter)
klaernie added a commit to klaernie/editorconfig-checker that referenced this issue Aug 30, 2024
@klaernie
feat(output): support output format github-actions (closes editorconf…
51218f5 
…ig-checker#317)

Now one can request `--format github-actions` and get the errors
returned in a format that should be parsable by Github Actions.

I decided against implementing the grouping feature (so errors would be
additionally grouped per file), since nested groups are not yet
supported - actions/toolkit#1001
Doing so would then break the use cases where a linter collection
like mega-linter or super-linter use groups themselves (e.g. to group
errors by linter)
klaernie added a commit to klaernie/editorconfig-checker that referenced this issue Sep 4, 2024
@klaernie
feat(output): support output format github-actions (closes editorconf…
7acfae7 
…ig-checker#317)

Now one can request `--format github-actions` and get the errors
returned in a format that should be parsable by Github Actions.

I decided against implementing the grouping feature (so errors would be
additionally grouped per file), since nested groups are not yet
supported - actions/toolkit#1001
Doing so would then break the use cases where a linter collection
like mega-linter or super-linter use groups themselves (e.g. to group
errors by linter)
@PatrickSchiefer
Copy link

Since this issue is already 2 years old, is there any chance to get this fixed soon?

@usimd usimd mentioned this issue Nov 6, 2024
Merged
@ranger-ross ranger-ross mentioned this issue Jan 3, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aminya @PatrickSchiefer