Skip to content

Commit 47ab230

Browse files
author
gitName
committed
update screenshot
1 parent 8c5c438 commit 47ab230

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

articles/api-center/enable-managed-api-analysis-linting.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,8 @@ With API analysis:
4141

4242
View an analysis summary and the analysis reports for your API definitions in the Azure portal. After API definitions are analyzed, the reports list errors, warnings, and information based on the configured API style guide.
4343

44+
In the API analysis report, also review the ruleset that was used for the analysis and the history of linting passes.
45+
4446
To view an analysis summary in your API center:
4547

4648
1. In the portal, navigate to your API center.
@@ -79,6 +81,9 @@ Before deploying the custom ruleset to your API center, validate it locally. The
7981

8082
Now, when you open an OpenAPI-based API definition file, a local linting operation is automatically triggered in Visual Studio Code. Results are displayed inline in the editor and in the **Problems** window (**View > Problems** or **Ctrl+Shift+M**).
8183

84+
> [!TIP]
85+
> API developers in your organization can use this local linting capability to help improve their API definitions before registering APIs in your API center.
86+
8287
:::image type="content" source="media/enable-managed-api-analysis-linting/validate-local-linting.png" alt-text="Screenshot of linting an API definition in Visual Studio Code." lightbox="media/enable-managed-api-analysis-linting/validate-local-linting.png":::
8388

8489
Review the linting results. Make any necessary adjustments to the ruleset and continue to test it locally until it performs the way you want.
-89.8 KB
Loading

0 commit comments

Comments
 (0)