You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then it correctly sets the log level to "trace" using the initialization option of air.logLevel, but if you change anything in the configuration after that then we try and re-pull the non-initialization version of air.logLevel (as we refresh everything) but this time around air.logLevel is None, so we end up reverting the log level back to "info", throwing out that initialization option of "trace".
This isn't a problem in VS Code because air.logLevel corresponds to both what we pull as the initialization option AND what we pull dynamically. In Zed I think they are separate, although I can't figure out how to set the non-initialization option of air.logLevel (it might not be possible).
We could say "if we pull air.logLevel=None and we have a previously set logLevel, then don't update the log level", but I worry about what that would mean for vs code, because in VS Code you may start with
"air.logLevel": "trace"
but then you may remove that line and expect it to go back to "info", but it won't if we do this. Although that may be a small price to pay for it to work mostly as expected elsewhere.
The text was updated successfully, but these errors were encountered:
If you set
Then it correctly sets the log level to
"trace"
using the initialization option ofair.logLevel
, but if you change anything in the configuration after that then we try and re-pull the non-initialization version ofair.logLevel
(as we refresh everything) but this time aroundair.logLevel
isNone
, so we end up reverting the log level back to"info"
, throwing out that initialization option of"trace"
.This isn't a problem in VS Code because
air.logLevel
corresponds to both what we pull as the initialization option AND what we pull dynamically. In Zed I think they are separate, although I can't figure out how to set the non-initialization option ofair.logLevel
(it might not be possible).We could say "if we pull
air.logLevel=None
and we have a previously setlogLevel
, then don't update the log level", but I worry about what that would mean for vs code, because in VS Code you may start withbut then you may remove that line and expect it to go back to
"info"
, but it won't if we do this. Although that may be a small price to pay for it to work mostly as expected elsewhere.The text was updated successfully, but these errors were encountered: