New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schema validation Uncaught Error #116
Comments
I don't think just clearing the value is a good solution. I think we should rather add some kind of |
Hi Sindre, I agree. I was only using the term 'clear' as documented here: I also agree some kind of |
isn't it |
I would have also expected that What would be the behavior of a In the meantime my current workaround is using this wrapper const makeStore = function (options) {
try {
return new Store({ ...options });
} catch (e) {
const store = new Store({ ...options, schema: null });
store.clear();
return return new Store({ ...options });
}
}; |
I have a schema which has the following entry:
I know config files are not meant to be hand edited, however, if the value of
dateFormat
is changed to a value outside of what's specified inenum
, then an 'Uncaught Error' is thrown in console instead of clearing the config value to its default on app start:So far I have only had this issue when using the enum validation on a string type.
The text was updated successfully, but these errors were encountered: