-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Use StyledStrings for Logging #51829
Conversation
Good to merge after #51869. |
b419d8b
to
a88ac9e
Compare
Fixed the merge conflict introduced in #52196. |
We could invoke |
I'm still interested in thoughts on
since I'm on the fence myself |
Other than the aforementioned bikeshed, I think this is just a review short of merging? |
ab03c94
to
0c0c385
Compare
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.
Aside from needing to fix some tests, this LGTM
You have triage permissions, so you can tag your PRs with "merge me" whenever you get them to a point that is ready and with tests passing (which is slightly more prompt at getting noticed than the "awaiting review" tag) |
da5e9e1
to
4e38ba7
Compare
|
Looking at the test state, it seems like we're good to go? Pkg isn't happy, but that seems to be that it has a bunch of test manifests that don't include I suspect I'm not the best person to take care of this Pkg-side issue. |
4e38ba7
to
ac71575
Compare
I think that test was recently deleted from Pkg due to other bugs in that precompile test. But there is a test that you will need to update (it is a list of dependencies of things in some packages, for testing purposes that it can read those lists):
|
Ah right, thanks. I think I've adjusted |
Transition from printstyled to the new approach to styling provided by StyledStrings. This both makes it possible for the styling used to be customised, and allows for other styled content to inherit/re-use the logging styles.
ac71575
to
ab0f1cf
Compare
Can be seen as a follow-on from #51829, also wants JuliaLang/StyledStrings.jl#37 to behave as expected.
Can be seen as a follow-on from JuliaLang#51829, also wants JuliaLang/StyledStrings.jl#37 to behave as expected.
This reverts commit 250916f.
This reverts commit 250916f.
This reverts commit 250916f.
This reverts commit 250916f.
This reverts commit 250916f.
Transition from printstyled to the new approach to styling provided by StyledStrings.
Along the way, this makes it possible to restyle logging should you desire to do so (for whatever reason), but also means that you can inherit the colours used in logging in other places.
This requires JuliaLang/StyledStrings.jl#3 and JuliaLang/StyledStrings.jl#6 to be resolved first.
In the meantime, a bikeshedding opportunity:
log.debug
(et al.) vs.logging.debug
(et al.)?