1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

Allow authentication with Google sign-in. This includes registering the user (on first login) and integrating with the current access token setup.

Describe the bug
Fix values rounding and display them according.

To Reproduce
Steps to reproduce the behavior:

1. Create several users using webchat publish
2. Chat a little using them
3. Go to the factory dashboard
4. See the mess

Expected behavior
Values should be rounded correctly.
Session duration is not calculated correctly and if the value is too big switch to secon

As of version ^2.0.0 of eslint-plugin-react-hooks the plugin now[ forbids top-level use*() calls more aggressively][pr].
See the official changelog and [corresponding commits][c] for more details.

To adapt to this change the peer & dev dependency version will be updated to the [latest minor/patch version][npm].

So.. It's a bit tricky until we reimplement the file state monitoring, because it could only accept non-glob path.

So we should probably use glob-parent or such.

Any help on this would be appreciated as we are not currently using this library with TypeScript