Describe the bug
When setting validation on a Collection, all properties need to be set, instead of just available. While this is not necessarily a problem, as the property can receive a empty [] containing no validators, a better qol improvement would be to change the typings of the validation object to a Partial<T>.
To Reproduce
Steps to reproduce the behavior:
- Create a Collection and add a Schema
- Add a Validation Object to the Collection
- You now see that all properties must be set
Expected behavior
I expect to only set the fields that I would want to validate
Screenshots
Additional context
This is a TypeScript only issue, as the bug in question stems from the implemented type system for the validation.
Describe the bug
When setting validation on a Collection, all properties need to be set, instead of just available. While this is not necessarily a problem, as the property can receive a empty
[]containing no validators, a better qol improvement would be to change the typings of the validation object to aPartial<T>.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to only set the fields that I would want to validate
Screenshots
Additional context
This is a TypeScript only issue, as the bug in question stems from the implemented type system for the validation.