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
{{ message }}
This repository has been archived by the owner on Jun 2, 2018. It is now read-only.
The mapping validation should be handled separately and not enforced within the Metadata classes. One reason is that because the Metadata classes have public properties, it is not really enforced anyway. A separate validation 'component' may be easier to maintain; having all validation logic in a single spot instead of spread over multiple classes
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The mapping validation should be handled separately and not enforced within the Metadata classes. One reason is that because the Metadata classes have public properties, it is not really enforced anyway. A separate validation 'component' may be easier to maintain; having all validation logic in a single spot instead of spread over multiple classes
The text was updated successfully, but these errors were encountered: