test(demo): OAS 3.1/3.2 demo fixtures for API Console v6 (W-23748889) - #906
Draft
alexpmule wants to merge 1 commit into
Draft
test(demo): OAS 3.1/3.2 demo fixtures for API Console v6 (W-23748889)#906alexpmule wants to merge 1 commit into
alexpmule wants to merge 1 commit into
Conversation
Adds two demo specs and registers them in the model manifest and demo app picker so the console has real OAS 3.1/3.2 models to render against: - oas31-webhooks.yaml: top-level webhooks + allOf/if-then-else/oneOf/anyOf - oas32-query-sse.yaml: QUERY method + text/event-stream (SSE) via itemSchema Both parse with conforms:true under AMF 5.11.x. Generated models are build artifacts (demo/models/*.json, gitignored), produced by generate-model once api-model-generator republishes with OAS 3.1/3.2 support (api-components/api-model-generator#20). W-23748889 (parent W-23735927).
alexpmule
added a commit
to api-components/api-model-generator
that referenced
this pull request
Aug 10, 2026
Bump version so CI publishes the new package with OAS 3.1/3.2 support. The publish job reads version from package.json and runs npm publish; without this bump the release would collide with the existing 0.3.1 and consumers (mulesoft/api-console#906) could not pick up the fix.
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
Adds two demo fixtures exercising OAS 3.1 and 3.2, registered in the model manifest and the demo app picker, so API Console v6 has real modern-spec models to render against.
Why
W-23748889 (parent W-23735927, TD-0333486). This WI is the foundation for the five rendering stories under the parent (oneOf/anyOf, if/then/else, QUERY, SSE, webhooks) — each needs real fixtures to build and test against.
Changes
demo/models/oas31-webhooks/oas31-webhooks.yaml— OAS 3.1.0: top-levelwebhooks(POST newPet) +allOf/if-then-else/oneOf/anyOfschema composition.demo/models/oas32-query-sse/oas32-query-sse.yaml— OAS 3.2.0:query:Path Item field (QUERY method) +/pets/eventsGET withtext/event-stream+itemSchema(SSE).demo/apis.json— manifest entries ("OAS 3.1"/"OAS 3.2").demo/element/app.js— demo picker entries.Generated models (
demo/models/*.json) are gitignored build artifacts, regenerated bynpm run generate-model.Verification
npm run build(rollup) → passes (created dist), no new warnings.conforms: true:oas31-webhooksemits Webhook nodes;oas32-query-sseemits QUERY + event-stream. No regression on existing RAML/OAS 3.0 fixtures.Stacked — merge order
mulesoft/api-console#905(spike/oas-3x-amf-bump): amf-client-js + api-model-generator dependency bump.getConfiguration— must merge + republish (0.4.0) sogenerate-modelproduces the 3.1/3.2 models. Until then the published0.3.1throwsUnknown API type: OAS 3.1and these fixtures generate no output.#905(and this PR) to the republishedapi-model-generatorversion, then merge this.🤖 Generated with Claude Code