You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click the image:icon-source-control-no-edits.png["",15,15] (*Source Control*) icon in the activity bar or use the keyboard shortcuts:
93
+
Click the image:anypoint-code-builder::icon-source-control-no-edits.png["",15,15] (*Source Control*) icon in the activity bar or use the keyboard shortcuts:
.. Select the element from the options, for example:
191
191
+
192
-
image::des-api-frag-ref-element.png["Reference an element in the fragment"]
192
+
image:anypoint-code-builder::des-api-frag-ref-element.png["Reference an element in the fragment"]
193
193
--
194
194
// end::ref-element[]
195
195
//
@@ -203,11 +203,11 @@ After adding the fragment to your spec, you can:
203
203
Place the cursor on the fragment reference and press Command+Click.
204
204
For example:
205
205
+
206
-
image::des-api-frag-goto-dependencies.png["Navigate to the fragment dependency"]
206
+
image:anypoint-code-builder::des-api-frag-goto-dependencies.png["Navigate to the fragment dependency"]
207
207
* View the dependency in the API Console:
208
208
+
209
209
Place the cursor on the fragment reference and click the
210
-
image:icon-api-console.png["",14,14] (*API Console*) icon to open the fragment in the console.
210
+
image:anypoint-code-builder::icon-api-console.png["",14,14] (*API Console*) icon to open the fragment in the console.
211
211
+
212
212
For more information, see xref:des-create-api-specs.adoc#review-spec-console[Review Your Spec in the API Console].
213
213
// end::after-add-fragment[]
@@ -227,15 +227,15 @@ Don't create the project within another project directory.
227
227
228
228
//
229
229
// tag::deploy-locally[]
230
-
. Click the image:icon-start-debug.png["",15,15] (*Start Debugging (F5)*) icon for *Debug Mule Application*.
230
+
. Click the image:anypoint-code-builder::icon-start-debug.png["",15,15] (*Start Debugging (F5)*) icon for *Debug Mule Application*.
231
231
+
232
232
Alternatively, if the *Start Debugging (F5)* icon is not present:
233
233
234
234
235
235
.. Click *Run and Debug*.
236
236
.. If a *Select debugger* dropdown menu appears, select *Mule Xml Debugger* to initiate the debugging session:
237
237
+
238
-
image::anypoint-code-builder::run-debug-imported-folder.png["Run and Debug button and Mule XML Debugger menu item"]
238
+
image:anypoint-code-builder::run-debug-imported-folder.png["Run and Debug button and Mule XML Debugger menu item"]
239
239
+
240
240
When the application deploys successfully, you see a `DEPLOYED` log message in the output panel:
241
241
+
@@ -255,7 +255,7 @@ When the application deploys successfully, you see a `DEPLOYED` log message in t
255
255
. From your IDE, open the Terminal window in the console:
256
256
257
257
* In the desktop IDE, select *View* > *Terminal*.
258
-
* In the cloud IDE, click the image:icon-menu.png["",18,18] (menu) icon, and select *Terminal* > *New Terminal*.
258
+
* In the cloud IDE, click the image:anypoint-code-builder::icon-menu.png["",18,18] (menu) icon, and select *Terminal* > *New Terminal*.
259
259
* For either IDE: Press Ctrl and then press the backtick key (`).
260
260
// end::open-terminal[]
261
261
//
@@ -368,7 +368,7 @@ To sync changes to project files with your repo, see <<sync-changes>>.
368
368
// tag::scm-stage-files-substep[]
369
369
.. Stage your files to your local repository by hovering over the *Changes* area (located after the *Commit* button) and clicking the image:anypoint-code-builder::icon-scm-add-changes.png["",15,15] (plus) icon.
370
370
+
371
-
image::anypoint-code-builder::start-scm-repo-stage-changes.png["Adding commit message for staged changes"]
371
+
image:anypoint-code-builder::start-scm-repo-stage-changes.png["Adding commit message for staged changes"]
372
372
+
373
373
Alternatively, you can stage a single file by clicking the plus icon for that file.
374
374
+
@@ -378,7 +378,7 @@ Staged files move from the *Changes* area in the Source Control panel to the *St
378
378
// tag::scm-commit-message-substep[]
379
379
.. Provide your a commit message for the files, and then click *Commit*, for example:
380
380
+
381
-
image::anypoint-code-builder::start-scm-repo-commit-staged.png["Commit message for staged changes"]
381
+
image:anypoint-code-builder::start-scm-repo-commit-staged.png["Commit message for staged changes"]
382
382
// end::scm-commit-message-substep[]
383
383
//
384
384
@@ -486,7 +486,7 @@ Make sure that you have access to AsyncAPI implementation features from the IDE:
486
486
487
487
.. Clicking *Join Beta* from the Anypoint Code Builder landing page
488
488
+
489
-
image::imp-asyncapi-join-beta.png["Administrator view of the Anypoint Code Builder landing page"]
489
+
image:anypoint-code-builder::imp-asyncapi-join-beta.png["Administrator view of the Anypoint Code Builder landing page"]
490
490
+
491
491
The *Join Beta* button is available only to your organization administrator.
492
492
.. Reviewing the terms and conditions of the beta program
@@ -511,10 +511,10 @@ When the AsyncAPI feature is available for your organization, the Anypoint Code
511
511
// tag::start-implementation[]
512
512
. From *Quick Actions*, click *Implement an API*:
513
513
+
514
-
image::implement-api-option-mat.png["*Implement an API* link highlighted in the *Getting Started* section"]
514
+
image:anypoint-code-builder::implement-api-option-mat.png["*Implement an API* link highlighted in the *Getting Started* section"]
515
515
. Complete the *Implement an API Specification* form:
516
516
+
517
-
image::implement-api-configure-in-task.png["Form for starting an implementation project"]
517
+
image:anypoint-code-builder::implement-api-configure-in-task.png["Form for starting an implementation project"]
0 commit comments