Omar Kohl
Omar Kohl
Ideally only once #276 is done because some of the dummy data contains multiple estimates per forecast, which can't be done with the API yet.
https://stackoverflow.com/questions/33644499/what-does-it-mean-when-they-say-react-is-xss-protected
* https://groups.google.com/g/golang-nuts/c/8boojTncXvs * https://dave.cheney.net/2015/11/05/lets-talk-about-logging * https://dave.cheney.net/2017/01/23/the-package-level-logger-anti-pattern * https://peter.bourgon.org/go-best-practices-2016/ The above links recommend not to use a global logger but instead pass it into the functions or make it a struct...
It does not work out of the box in Gitpod (GH Codespaces untested). When setting an additional ENV variable `ELECTRON_RUN_AS_NODE=1` it complains about a missing dependency. https://docs.cypress.io/guides/continuous-integration/introduction#Running-headless-tests-without-Xvfb Probably it would...
Currently the production builds no longer include dummy data. If such a button/function existed it would be possible to re-add it.
The ent-experiment branch contains a revert of the revert and can be used to experiment with ent.