-
Notifications
You must be signed in to change notification settings - Fork 176
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
feat(utils): formatTree
utility
#223
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #223 +/- ##
==========================================
- Coverage 61.13% 60.13% -1.00%
==========================================
Files 13 14 +1
Lines 1379 1480 +101
Branches 58 58
==========================================
+ Hits 843 890 +47
- Misses 536 590 +54 β View full report in Codecov by Sentry. |
9fd88f7
to
7e34ab5
Compare
Thanks for working on this it is a really useful addition! π₯ I have made a couple of reactors to keep the feature as an opt-in util. Despite normal log levels and also box where formatting for them is optional, with tree, when reporters don't implement it (basic, json, browser, etc) it will lead to and unreadable output. I am thinking to introduce more of formatting utils like this |
π Linked issue
β Type of change
π Description
Add a logger that display a tree of items. This can be used in Nitro when pages are prerendered.
Supports:
π Checklist