You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the validation side, the validation will be an option. Fields will not be mandatory by default. They will be checked only when the user asks to validate and not at the time of creation. This will enforce the user to be able to create and dump eventually partial documents that may not yet be fully valid.
This can be established by introducing a validate flag in both the parsers (tagvalue and rdf) and validating only when the flag is set.
While the parser methods still don't have a validate flag (see e.g. this section), there doesn't seem to be a lot of people impacted by this shortcoming. I will close this for the time being; the upcoming refactoring will validate in a separate layer anyway, and we can add a flag there.
On the validation side, the validation will be an option. Fields will not be mandatory by default. They will be checked only when the user asks to validate and not at the time of creation. This will enforce the user to be able to create and dump eventually partial documents that may not yet be fully valid.
This can be established by introducing a
validate
flag in both the parsers (tagvalue and rdf) and validating only when the flag is set.@pombredanne Should I create a PR for this one ?
The text was updated successfully, but these errors were encountered: