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
(Love this extension - sending tons of data to Algolia, and it's working great.)
The local env really suffers from all the debug logging being thrown; it looks like, for me, every file sync'd logs 3 (large) log entries:
1 DEBUG log
2 INFO logs
It's about ~100 lines in my terminal window. This makes any local Firebase Emulator work very, very spammy.
I would love a way to disable this - perhaps via an entry in firestore-algolia-search.env? My perfect implementation would be to leave WARN logs and higher enabled, so perhaps the config line is like MIN_LOG_LEVEL or something. But it could also just be LOGS_DISABLED and that would serve me just fine. :)
(I am (personally) OK with these logs staying in production, though honestly I could imagine that being configurable as well for extremely high workloads that want to minimize logging.)
Thanks for the great extension!
The text was updated successfully, but these errors were encountered:
(Love this extension - sending tons of data to Algolia, and it's working great.)
The local env really suffers from all the debug logging being thrown; it looks like, for me, every file sync'd logs 3 (large) log entries:
DEBUG
logINFO
logsIt's about ~100 lines in my terminal window. This makes any local Firebase Emulator work very, very spammy.
I would love a way to disable this - perhaps via an entry in
firestore-algolia-search.env
? My perfect implementation would be to leaveWARN
logs and higher enabled, so perhaps the config line is likeMIN_LOG_LEVEL
or something. But it could also just beLOGS_DISABLED
and that would serve me just fine. :)(I am (personally) OK with these logs staying in production, though honestly I could imagine that being configurable as well for extremely high workloads that want to minimize logging.)
Thanks for the great extension!
The text was updated successfully, but these errors were encountered: