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 Aug 26, 2020. It is now read-only.
When built-in schematron validation is available, entity services can take advantage of it by placing a compiled version of entity services sch. schemas in the modules directory.
This could be checked in here to github or in svn directly
The text was updated successfully, but these errors were encountered:
Since 9.0-8 has reached functionally complete date, this mod should be queued up for work. It's a non-functional change but it would be good to knock it out with some chance to check out regressions
I've done the initial foray into the switch. It seems like it's working. However the new implementation doesn't report the same failures are the previous one. I'd like to find out how to control the reporting in the new implementation. It might be that we can just modify the keys to be more precise and elicit the more granular error that we're looking for.
As an example of what im talking about -- an entity with missing info notes that there is no primary key -- which while strictly true is not the most relevant validation error for such a descriptor.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When built-in schematron validation is available, entity services can take advantage of it by placing a compiled version of entity services sch. schemas in the modules directory.
This could be checked in here to github or in svn directly
The text was updated successfully, but these errors were encountered: