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
Is your feature request related to a problem? Please describe.
The problem arises when trying to control log output in different environments using the StackedLogger class. Currently, there is no straightforward way to specify which logs are displayed in production versus development environments.
Describe the solution you would like
I propose adding functionality to the StackedLogger class that allows developers to specify a default log filter directly through the @StackedApp annotation. This would involve enhancing the logger setup to accept a filter parameter that determines which log messages are appropriate for different build variants or environments. For example:
The text was updated successfully, but these errors were encountered:
FilledStacks
added
Improvement
An issue to improve existing functionality
new feature
Requires planning and detailed comments of what will be done to build this
and removed
new feature
Requires planning and detailed comments of what will be done to build this
labels
Apr 25, 2024
Is your feature request related to a problem? Please describe.
The problem arises when trying to control log output in different environments using the StackedLogger class. Currently, there is no straightforward way to specify which logs are displayed in production versus development environments.
Describe the solution you would like
I propose adding functionality to the StackedLogger class that allows developers to specify a default log filter directly through the @StackedApp annotation. This would involve enhancing the logger setup to accept a filter parameter that determines which log messages are appropriate for different build variants or environments. For example:
Additional Context
No response
The text was updated successfully, but these errors were encountered: