Marin Aldimirov

The issue can be resolved by using a `.eslintignore` file. In my case is seems eslint was trying to lint the `node_modules` and adding a eslintignore file with just node_modules...

@Prat041192 could it be you have misspelled? In your comment you are missing a `l`. `node_modues/*` should be `node_modules/*`

As @scerelli I also wanted the mock to happen in a separate place so it can be used by all tests. Placing the following code in `/__mocks__/react-native-fetch-blob.js` seems to work...

You are right. It can be done using `refineType` and a custom type. The only downside I see to this is that you need to recreate the same `joi` validation...

The PR is ready. This functionality would be more viable than `refineType` in the cases where you want to change the default validation per instance, not globally for a specified...

`anyOf` and `type` are two different validation keywords. I don't think you can use two validation keywords alongside in the same schema. At least I don't see that allowed in...

Yes, I think the schema is not valid. And I don't know why `jsonschema` and `ajv` would behave like that. I would speculate that their code does not stop execution...

Mostly it's out of principle, yes. We had only 1 issue with `enjoy` where we had a mistyped schema. Roughly something like the following: ```javascript { oneOf: [...], type: 'object',...

Well I also only learned this by the [github thread](https://github.com/json-schema-org/json-schema-spec/issues/733), not by the documentation itself. I agree documentation is vague on this topic and should be more explicit.

I guess. At this point the choice is entirely yours. Since these problems we have switched to use `ajv`, which follows JSON Schema very strictly and even has a schema...