-
There are a couple issues with the `config` module validation right now that would be nice to address before we move to regular deployments.
1) If you leave a key without a value, e.g. `LOG_LEVEL=`…
-
Convert existing uses of joi over to config-schema
-
## 🐛 Bug Report
The following errors were observed after upgrading to alpha 59:
* `ValidationError: "navbar.title" is not allowed to be empty`
* `ValidationError: "navbar.title" is required`
…
-
-
Since create listing api uses form data hence celebrate joi does not work properly. So need to find a away around.
Try adding the joi validation after the multer middleware. Check if that helps.
-
Hi, we use a lot of validation in browser runtime with "joi" library. Could you please add some benchmarks about this package?
-
First, thank you very much for Docusaurus, it's a great tool that we use for another open-source project, Gladys Assistant 🙂
When I read the doc here: https://v2.docusaurus.io/fr/docs/next/api/them…
-
#### Status: 400 Bad Request even i throw true info any help ??
response
{
"error": null,
"value": {
"name": "Hammed",
"number": "32313123123"
}
* *node version : v16.…
Oskku updated
2 years ago
-
Currently we're relying on TypeScript to find errors within the alert / action types. We should use Joi or config-schema to do the validation within the register function.
-
I recommend switching to [vlid.js](https://github.com/vlucas/vlid) for optimizing purposes. It is a similar library, but 10x smaller and better for as an example the frontend where the 140kb of joi wo…