Use supported Zed captures for log levels

[ayakutt]

Summary

This PR fixes #6, where INFO, WARN, and ERROR log levels were not highlighted in some Zed themes such as One Dark.

The root cause was that the extension used these captures in highlights.scm:

• @info
• @warning
• @error

Those are not part of Zed's standard theme-supported syntax captures, so in themes that do not define them explicitly, those tokens fall back to the default foreground color.

Change

This PR updates the log level captures to use supported captures with reliable theme fallbacks:

• info -> @hint.info
• warn -> @constant.warning
• error -> @keyword.error

trace and debug were already using compatible captures and were left unchanged.

Result

INFO, WARN, and ERROR now render with consistent syntax coloring across themes instead of appearing unstyled.

Closes #6

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @ayakutt on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[ayakutt]

@cla-bot check

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @ayakutt on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @ayakutt on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

[ayakutt]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[MrSubidubi]

Thanks for this!

We support more captures these days, thus this is not the optimal approach. Can we instead perhaps add these new captures as fallback captures should the other captures not be set? So keep the current ones and add these as fallbacks only

[ayakutt]

We support more captures these days, thus this is not the optimal approach. Can we instead perhaps add these new captures as fallback captures should the other captures not be set? So keep the current ones and add these as fallbacks only

Thanks for the review @MrSubidubi !

I have a concern about this approach though.

The original issue (#6) is that @info, @warning, and @error are not styled by Zed themes, which is why colors aren't rendering for those log levels. If we keep those as the primary captures and add @hint.info, @constant.warning, @keyword.error as fallbacks, the fallbacks would only be used when the primary captures are not set. Since @info/@warning/@error likely still exist as valid captures (just unstyled), the fallback would never trigger and the issue would persist.

I think replacing them entirely is the right approach here, the original captures simply aren't supported by themes, which is the root cause of the bug.

[MrSubidubi]

Nope, see the section on how this applies to themes - if the theme does not specify any highlighting for the primary capture, we will fall back to the secondary one. The only thing here relevant is whether the theme supports that capture and the issue originates from the fact that most themes don't. However, if they do, everything will work as expected. You should also be able to test this locally with the theme you tried this out initially

[ayakutt]

@MrSubidubi Thanks, that makes sense. I updated the query to keep the original captures as the preferred captures and added the supported captures as fallbacks:

(info) @hint.info @info
(warn) @constant.warning @warning
(error) @keyword.error @error

I also squashed the branch down to a single commit. Could you take another look when you have a chance?

[MrSubidubi]

Awesome, thank you so much! And congratulations to your first contribution! 🎉