Example
Example copied to clipboard
metarhia
Metarhia application example for Node.js 🟢
Closes: https://github.com/metarhia/Example/issues/238 - [x] tests and linter show no problems (`npm t`) - [ ] tests are added/updated for bug fixes and new features - [x] code is properly formatted...
Closes: https://github.com/metarhia/Example/issues/263 The cause appears to be a tiny typo in a first guard line at https://github.com/metarhia/Example/blob/2435b8e643af3fc4a62fea1f3f20bdedc1e1d9c1/application/domain/tests/api.js#L2-L3 Reverse of the check enables assertions and cases from the script. Console result...
### Describe the bug Example project has tests for API in the [`application/domain/tests`](https://github.com/metarhia/Example/tree/master/application/domain/tests) folder. Specifically two tests `http.test.js` and `ws.test.js` running the same test cases from `api.js`, e.g. https://github.com/metarhia/Example/blob/2435b8e643af3fc4a62fea1f3f20bdedc1e1d9c1/application/domain/tests/api.js#L11-L14 It...
### Way to reproduce an error 1. Enable execution of [domain.time.start hook](https://github.com/metarhia/Example/blob/master/application/domain/time/start.js) by switching [`config.examples.bus`](https://github.com/metarhia/Example/blob/2435b8e643af3fc4a62fea1f3f20bdedc1e1d9c1/application/config/examples.js#L2) value to `true` 2. `node server.js` 3. There is a log message in a console...
in the session recovery example, potential error application/api/auth.2/restore.js ``` ({ access: 'public', method: async ({ token }) => { const restored = context.client.restoreSession(token); if (restored) return { status: 'logged' };...
This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade redis from 4.6.10 to 4.6.11. :information_source: Keep your dependencies up-to-date....
I don't know if this is the correct way of passing the error class between files in API, but this is how in theory error should be used. The idea...
