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
## Problem
The "Logging" section explains LOG_LEVEL and LOG_FORMAT but does not:
Mention the default values for these variables.
Provide examples of how to set them in a .env file or during runtime.
This lack of information may confuse new developers who are integrating logging functionality.
Additionally, the list of possible values for LOG_LEVEL and LOG_FORMAT is missing. Adding a table with these details would make the documentation clearer.
## Solution
Add a table or list with default values for LOG_LEVEL and LOG_FORMAT. For example:
Variable
Possible Values
Default Value
LOG_LEVEL
DEBUG, INFO, WARN, ERROR, OFF
INFO
LOG_FORMAT
PRETTY, JSON
JSON
Provide examples of how to set these variables in a .env file or inline during runtime, for example:
LOG_LEVEL=DEBUG LOG_FORMAT=PRETTY yarn start
## Nice to Have
-Warnings for invalid LOG_LEVEL or LOG_FORMAT values would be very useful.
-Add a show-log-config command to display the current logging configuration for easier debugging.
The text was updated successfully, but these errors were encountered:
## Problem
The "Logging" section explains
LOG_LEVEL
andLOG_FORMAT
but does not:.env
file or during runtime.This lack of information may confuse new developers who are integrating logging functionality.
Additionally, the list of possible values for
LOG_LEVEL
andLOG_FORMAT
is missing. Adding a table with these details would make the documentation clearer.## Solution
Add a table or list with default values for
LOG_LEVEL
andLOG_FORMAT
. For example:Provide examples of how to set these variables in a
.env
file or inline during runtime, for example:## Nice to Have
-Warnings for invalid
LOG_LEVEL
orLOG_FORMAT
values would be very useful.-Add a
show-log-config
command to display the current logging configuration for easier debugging.The text was updated successfully, but these errors were encountered: