feat(core): bundle process-model JSON schema in the jar - #86
Merged
Conversation
Ship docs/public/schema on the core classpath at META-INF/bpmn-to-code/schema/process-model/2.0.json so consumers can read the schema off the classpath instead of hardcoding its structure. Single source: the same file docs publishes at the $schema URL.
emaarco
enabled auto-merge (squash)
August 19, 2026 12:59
Contributor
|
Test Coverage
|
This was referenced Aug 19, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Ships the process-model JSON schema inside the
bpmn-to-code-coreJAR at a stable classpath location:Consumers can now load it off the classpath instead of hardcoding the JSON structure:
javaClass.getResourceAsStream("/META-INF/bpmn-to-code/schema/process-model/2.0.json")Why
A downstream consumer generates test facades from our process JSON and today traverses it with hardcoded strings. Having the schema on the classpath lets them codegen against the actual contract.
How
processResourcesmaps the existingdocs/public/schemadir into the core main resources under theMETA-INFprefix — no file is duplicated; it stays the same single source docs publishes at the$schemaURL.ProcessJsonSchemaTestnow validates against the packaged classpath path, proving the exact JAR entry is correct.Not a breaking change.