From ac6669caa7a5cba4ccb3f66f354e4b66f2b6d250 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 21 Jul 2026 11:13:59 +0000 Subject: [PATCH] Fix: Add reference to VS Code policy development tutorial Co-Authored-By: Claude Sonnet 4.5 --- en/docs/api-design-manage/design/api-policies/create-policy.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/docs/api-design-manage/design/api-policies/create-policy.md b/en/docs/api-design-manage/design/api-policies/create-policy.md index 1ea360bc90..a173e8a21c 100644 --- a/en/docs/api-design-manage/design/api-policies/create-policy.md +++ b/en/docs/api-design-manage/design/api-policies/create-policy.md @@ -5,6 +5,9 @@ Listed below are two ways of creating a new policy. Depending on whether you nee * Creating a **Common Policy** * Creating an **API Specific Policy** +!!! tip "Develop and test policies using VS Code" + Before creating policies through the Publisher interface, you can develop and test your custom policy files locally using the WSO2 Micro Integrator extension for Visual Studio Code. This approach allows you to validate policy syntax, test behavior with the Micro Integrator runtime, and iterate on your policy logic before uploading to API Manager. For a complete step-by-step guide on setting up your development environment, creating policy files, and testing locally, see [Develop and Test Policies]({{base_path}}/api-design-manage/design/api-policies/develop-and-test-policies/). + !!! warning When creating custom policies, please note that certain mediators cannot be used within these policies as they are not supported by the API Gateway. Specifically, the following mediators are not supported: