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
First, the docs are not clear what SupabaseClientBuilder.defaultLogLevel does. I assume it's the level at and above which log messages are not ignored. I think the docs should be updated to make that explicit.
Second, Kermit has its own config for this. If you set a global minSeverity, the higher of that and the one set in SupabaseClientBuilder will be the observed value. If I want to set the default minSeverity to Info for my other loggers, but override that to Debug for Supabase loggers, that doesn't appear to be possible. In KermitSupabaseLogger, when level is set, it should set logger.mutableConfig.minSeverity, including during initialization.`
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
First, the docs are not clear what
SupabaseClientBuilder.defaultLogLevel
does. I assume it's the level at and above which log messages are not ignored. I think the docs should be updated to make that explicit.Second, Kermit has its own config for this. If you set a global
minSeverity
, the higher of that and the one set inSupabaseClientBuilder
will be the observed value. If I want to set the defaultminSeverity
toInfo
for my other loggers, but override that toDebug
for Supabase loggers, that doesn't appear to be possible. InKermitSupabaseLogger
, whenlevel
is set, it should setlogger.mutableConfig.minSeverity
, including during initialization.`Do you agree with this and want me to make a PR?
Beta Was this translation helpful? Give feedback.
All reactions