Split up schema and add C8 JSON Schema #41
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Uses `json-schema-ref-parser` to bundle schema chunks into a final one.
Move base element template definitions into a `defs` sub folder
pinussilvestrus
force-pushed
the
561-c8-schema
branch
from
7a0cbe4 to
90ef334
Compare
|
Also, find some more reasoning about this initiative in my lightning talk. |
bpmn-io-tasks
bot
added
needs review
pinussilvestrus
requested review from
a team,
philippfromme and
marstamm
and removed request for
a team
6 tasks
|
Note: this PR still includes the term |
This was referenced Feb 14, 2022
Merged
philippfromme
approved these changes
Feb 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to bpmn-io/bpmn-js-properties-panel#561
This demonstrates how to split up the existing JSON Schema into smaller chunks (
src/defs) and generate it back to the exporting schema asbuildstep.Furthermore, it's adding support for the new C8 templates bindings on top:
zeebe:taskDefinition:typezeebe:taskHeader(binding.keyis required)zeebe:input(binding.nameis required)zeebe:output(binding.sourceis required)optionalfor inputs and outputsoptionalforconstraints.notEmpty = trueThings to clarify in kick off (can still be changed later)
resources/*.json)? schema / platform / cloud vs. C7 / C8?