Skip to content

W-23425476-Add-OAS-3-0-support-CP #680

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.

Sign up for GitHub

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

Open
Crispy-Salesforce wants to merge 2 commits into
base: MS2026-07-21-ACB-1-24
Choose a base branch
from
Open

W-23425476-Add-OAS-3-0-support-CP #680

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
314580c
W-23425476-Add-OAS-3-0-support-CP
Crispy-Salesforce Jul 16, 2026
05141ab
W-23425476-Address-SME-feedback-CP
Crispy-Salesforce Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion code-builder-home/modules/ROOT/pages/_partials/acb-reusable-steps.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,7 +271,7 @@ Anypoint Code Builder supports scaffolding these schema fragment files if they'r
| *AsyncAPI* | Yes | Yes | No
| *GraphQL* | No | No | Yes
| *OData* | No | No | Yes
| *REST* | No | No | Yes
| *REST* | No | Yes | Yes
| *SOAP* | No | No | Yes
|===

Expand Down
4 changes: 2 additions & 2 deletions code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"]
//LOGO (web, desktop, or both)
// include::partial$acb-ide-logos.adoc[tags="both-ides"]

// TODO: How does this work in OAS?

Using Anypoint Code Builder, you can create your own API fragments and publish them to Anypoint Exchange to share with other people,
add fragments from Exchange to your API specification,
or create fragments in your project to add directly to your API specification.
Expand Down Expand Up @@ -185,6 +183,8 @@ To add an API spec fragment to a spec:
** RAML specs: Use the `!include` directive.
--
+
For OAS 3.0 APIs, scaffolding supports `$ref` API fragments from Exchange, including fragments with transitive dependencies, for any Mule runtime version. DataSense resolves types defined in fragment files when you scaffold into a Mule project that uses a supported Mule runtime version (currently Mule 4.9.19 and Mule 4.11.6).
+
[tabs]
====
OAS Example::
Expand Down