javier-garcia-meteologica
javier-garcia-meteologica
Ability to listen to exceptions or use custom exception handlers instead of sending to console.error
@AlexandrHoroshih, I think that your idea would be great for my usecase. @zerobias > You should not run [...] dangerous code in pure methods like `.on` and `.map` I understand...
Ability to listen to exceptions or use custom exception handlers instead of sending to console.error
It's not possible to refactor the global error handler because it's also used outside of effector, for instance it also handles errors captured in `window.addEventListener('error' | 'unhandledrejection')`.
Ability to listen to exceptions or use custom exception handlers instead of sending to console.error
I see, thank you!
`req.body` is expected to be typed as `{ id: string }`. The problem comes from non-validated user input. Static analysis is not enough to detect malicious input present at runtime.
> at some point have cast it to that without checking it Yes, in this issue the developer can definitely be blamed for not validating input. E.g. ```ts router.post('/example', (req,...
Why not turn it upside down and use a modular approach? Declare a structured interface for each table and use it to call `sql` or shorthand functions. ```ts export namespace...
I've also run into problems with objects that have some keys mapped to undefined. Apart from `WHERE` clauses, this problem occurs also with insert/upsert values, which are handled by `vals()`...
Related to #46, #97 A month ago I added the patch to ignore undefined keys in the branch [javier-garcia-meteologica/zapatos#ready](https://github.com/javier-garcia-meteologica/zapatos/commits/ready), the commit is named [Ignore undefined keys](https://github.com/javier-garcia-meteologica/zapatos/commit/4eecc6d2bfe93cefb0a4bcdf67fb629bc3715e6f). On top of `cols()`...
Let me convince you why your original idea of ignoring `undefined` keys is as consistent as the current state of `zapatos`. > [E]verything would work if I used `user` in...
It would be nice to allow specifying extra containers. The option would be specified at the time of plugin createion `{ extraContainers?: RegExp[] }`. It would extend the default continer...