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
Copy file name to clipboardExpand all lines: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,3 +45,21 @@ Open browser at https://localhost:3000 and accept invalid cert (may not work in
45
45
```sh
46
46
yarn test
47
47
```
48
+
49
+
## Logging
50
+
51
+
Client-side logs are disabled by default in production builds and enabled by default in a development environment. In production, logging can be turned on by adding a couple keys to your browser's `localStorage`. Simply run these two JS statements in you browser's DevTools console:
The value for `debug` is a namespace filter which determines which portions of the app to display logs for. The namespaces currently used by the app are as follows:
58
+
59
+
-`main`: logs general application messages
60
+
-`action`: logs all actions that modify the internal application state
61
+
-`grpc`: logs all GRPC API requests and responses
62
+
63
+
Example filters: `main,action` will only log main and action messages. `*,-actions` will log everything except action messages.
64
+
65
+
The value for `debug-level` determines the verbosity of the logs. The value can be one of `debug`, `info`, `warn`, or `error`.
0 commit comments