-
Notifications
You must be signed in to change notification settings - Fork 4
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
Initial Validator #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added two comments, other than that 👍
I'll update the project to make it even more generic and not element-template specific. |
I'd even go for Validator#validate
Validator#validateAll Instead of Validator#validateTemplate
Validator#validateTemplates |
Always provide a `valid` property for both single and collection validation.
I've pushed a few commits on top:
The last two things are up for debate. I personally believe whoever uses the library will do his / her filtering / collecting of errors anyway, so the more generic API would work for me, too. Added a test case, how extracting of valid templates looks: https://github.com/bpmn-io/json-schema-validator/pull/1/files#diff-8f573ab0dcdbf810d70135136d063a35a616b34aafaa78566ba814952eb1dc89R66. Note, as mentioned, that an app likely does more. It will likely collect both valid templates and errors at the same time. |
I like the more generic approach. Let's make the most out of it 👍 |
I guess this one is ready to be released? |
Yes! I plan to do the initial release for it today 👍 |
I would assume the API is stable, so |
Yes. Starting with a |
I'd start with |
Yeah, let's keep the stableness open. |
Related to camunda/element-templates-json-schema#11
Which issue does this PR address?
Related to camunda/element-templates-json-schema#11
Acceptance Criteria
Definition of Done