github/lodestar
1
1
Fork 0
mirror of https://github.com/ChainSafe/lodestar.git synced 2026-01-09 15:48:08 -05:00
Code Issues Packages Projects Releases Wiki Activity

Remove outdated logging framework in style guide (#5370)

Browse Source 
Replaced by "Logging policy" section added in https://github.com/ChainSafe/lodestar/pull/5299
This commit is contained in:
Nico Flaig
2023-04-17 23:01:10 +02:00
committed by GitHub
parent 6cfc518517
commit 3ee1d8a5ac
1 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
CONTRIBUTING.md
View File

@@ -142,13 +142,6 @@ We're currently experimenting with hosting the majority of lodestar packages and
- Use `/** **/` commenting format for documenting a function/variable.
- Code whitespace can be helpful for reading complex code, please add some.
- For unit tests, we forbid import stubbing when other approaches are feasible.
- Logging framework: When determining which log level to use for providing information to users, consider the level of importance and whether the alert is actionable (Warning, Error, Fatal).
- Trace: Describes events showing step by step execution which can be ignored during standard operation.
- Debug: Useful information for debugging purposes.
- Info: Purely informative logs which can be ignored during normal operation.
- Warning: Unexpected behaviour, but the application continues to function and key operations are unaffected.
- Error: One or more main functionalities are not working, preventing some functions from working properly.
- Fatal: One or more main functionalities are not working and preventing the application from fulfilling its duties.
## Logging policy