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
Copy file name to clipboardExpand all lines: content/3-BlogsTranslated/3.1-Blog1/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Many organizations require dynamic API routing capabilities to support their evo
20
20
21
21
With this new launch, you can implement dynamic routing logic with a simple declarative configuration within the custom domain name settings. The new routing rule mechanism allows you to make routing decisions based on HTTP headers, base paths, or a combination of both. Developers are no longer required to create new or alter existing paths to smoothly transition between API versions, they can simply specify the desired value in the request HTTP header. Among other possibilities, you can implement cell-based architecture routing, A/B testing, or dynamic backend selection based on [hostname](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html#wildcard-custom-domain-names), tenant ID, accepted response media type, or cookie value. By implementing routing logic directly within the API Gateway, you can eliminate proxy layers and complex URL structures while maintaining fine-grained control over your API traffic. This new feature seamlessly integrates with existing API Gateway capabilities and supports both public and private REST APIs. The following diagram shows how you can use routing rules for header and base-path based routing. This example uses a single level resource /products to show path matching, however depending on your use-case you could also use multi-level paths like **/products/items**.
Copy file name to clipboardExpand all lines: content/3-BlogsTranslated/3.1-Blog1/_index.vi.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Nhiều tổ chức yêu cầu khả năng định tuyến API động để đ
20
20
21
21
Với Dynamic Routing Rules, bạn có thể triển khai logic định tuyến động bằng một cấu hình khai báo đơn giản trong phần cài đặt custom domain name. Cơ chế routing rule mới cho phép bạn đưa ra các quyết định định tuyến dựa trên HTTP headers, base paths, hoặc kết hợp cả hai. Các nhà phát triển không còn cần phải tạo mới hoặc thay đổi các path hiện có để chuyển đổi mượt giữa các phiên bản API, họ chỉ cần chỉ định giá trị mong muốn trong request HTTP header. Trong số các khả năng khác, bạn có thể triển khai định tuyến kiến trúc cell-based, A/B testing, hoặc lựa chọn backend động dựa trên [hostname](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html#wildcard-custom-domain-names), tenant ID, accepted response media type, hoặc cookie value. Bằng cách triển khai logic định tuyến trực tiếp trong API Gateway, bạn có thể loại bỏ các proxy layers và các cấu trúc URL phức tạp trong khi vẫn duy trì quyền kiểm soát chi tiết với traffic API của bạn. Tính năng mới này tích hợp liền mạch với các khả năng hiện có của API Gateway và hỗ trợ cả REST APIs công khai và riêng tư. Sơ đồ sau cho thấy cách bạn có thể sử dụng routing rules cho định tuyến dựa trên header và base-path. Ví dụ này sử dụng một tài nguyên cấp một /products để minh họa khớp path, tuy nhiên tùy thuộc vào use-case bạn cũng có thể dùng các path nhiều cấp như /products/items.
Hình 1. Sử dụng routing rules cho định tuyến dựa trên header và base-path
26
26
@@ -125,7 +125,7 @@ Trong các kịch bản như API versioning, bạn có thể tạo rule để đ
125
125
126
126
Header-based routing cũng đơn giản hóa việc A/B testing bằng cách cho phép bạn định nghĩa các nhóm client dựa trên custom headers, cho phép thực hiện thử nghiệm có kiểm soát với các cấu hình khác nhau. Bạn có thể tạo rule kiểm tra một custom header như x-test-group để định tuyến người dùng cụ thể tới các implementation API khác nhau. Hệ thống priority đảm bảo hành vi định tuyến có thể dự đoán -- khi nhiều rule khớp với một request, rule có số priority thấp nhất (tức là precedence cao nhất) sẽ quyết định định tuyến. Việc kết hợp cả header và path conditions trong một rule duy nhất cho phép các kịch bản định tuyến phức tạp, ví dụ như định tuyến theo version cụ thể cho các tài nguyên API cụ thể thay vì toàn bộ API, như minh họa trong sơ đồ sau.
Copy file name to clipboardExpand all lines: content/3-BlogsTranslated/3.2-Blog2/_index.md
+15-16Lines changed: 15 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,7 @@ pre: " <b> 3.2. </b> "
8
8
9
9
[Click here to read the orignal post](https://aws.amazon.com/vi/blogs/devops/introducing-an-agentic-coding-experience-in-visual-studio-and-jetbrains-ides/)
10
10
11
-
12
-
*by Artur Rodrigues and Neeraj Handa on 05 JUN 2025*
11
+
_by Artur Rodrigues and Neeraj Handa on 05 JUN 2025_
13
12
14
13
Developers spend countless hours on repetitive tasks like debugging code, writing unit tests, and validating build processes – time that could be better spent on innovation and problem-solving. To address these challenges, Amazon Q Developer has expanded its intelligent coding assistant capabilities to Visual Studio and JetBrains Integrated development environments (IDEs). This new agentic experience works proactively on your behalf, automatically analyzing your workspace, generating code fixes, and executing commands to streamline your development workflow.
15
14
@@ -35,45 +34,45 @@ Context management extends to configuration through the .amazonq/rules/ director
35
34
36
35
Let us walk you through two use cases. In our example, we will use the Visual Studio IDE. Similar agentic capabilities are now supported in [JetBrains IDEs](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-in-IDE.html#supported-ides-features) as well. We invite you to follow along by cloning the [Bob’s Used Books sample repo](https://github.com/aws-samples/bobs-used-bookstore-sample) and opening it in Visual Studio 2022. Don’t forget to add or update the [Amazon Q Developer extension](https://marketplace.visualstudio.com/items?itemName=AmazonWebServices.AWSToolkitforVisualStudio2022).
37
36
38
-
***Creating unit tests***
37
+
**_Creating unit tests_**
39
38
40
39
The **Bookstore.Domain** project contains domain objects such as **Book** and **ShoppingCart**.
We want to add unit tests for the **ShoppingCart** class. Let’s ask Amazon Q Developer to create unit tests for **ShoppingCart**. We also want Amazon Q Developer to follow the existing pattern of creating test classes in a separate test project.
53
52
54
53
By default, the agentic experience is on. If you are in the planning phase of the Software Development Lifecycle (SDLC) and prefer to use a traditional back-and-forth chat, you can turn the agentic experience. To toggle the agentic experience on and off, choose the angle bracket pair in the bottom left corner of your Q Developer chat window.
55
54
56
-
Then, we ask Q Developer *“Can you create a test for @ShoppingCart.cs? Look at existing test and use the same libraries”*. First, notice that we are giving a command instead of just asking a question. Second, we are referencing the file ShoppingCart.cs explicitly to provide Q Developer the appropriate context. In the following image, you can see that Q Developer is acting on our behalf. In agentic coding mode, Q Developer can take actions and run commands. In our example, it is reading files, writing to files, and running commands with your permission.
55
+
Then, we ask Q Developer _“Can you create a test for @ShoppingCart.cs? Look at existing test and use the same libraries”_. First, notice that we are giving a command instead of just asking a question. Second, we are referencing the file ShoppingCart.cs explicitly to provide Q Developer the appropriate context. In the following image, you can see that Q Developer is acting on our behalf. In agentic coding mode, Q Developer can take actions and run commands. In our example, it is reading files, writing to files, and running commands with your permission.
Using commands, Q Developer was able to analyze our solution structure, understand that we have a project called **Bookstore.Domain.Tests**, and create a new file containing unit tests for **ShoppingCart**.
We can verify that there is a new file called **ShoppingCartTests** in the **Bookstore.Domain.Tests** project, which is aligned with our existing test creation strategy.
@@ -83,30 +82,30 @@ In the following example, we will demonstrate the power of the agentic coding ex
83
82
84
83
In our example, we have deliberately misspelled one of the methods in the **IShoppingCartRepository** interface. The **AddAsync** method is now incorrectly spelled **AddAsyn**.
When we try to build the **Bookstore.Domain** project, we get a build error as expected. Let’s ask Q Developer to fix the error. Without the agentic coding experience, we would have to copy the text of the build error into the chat window and ask Q Developer to provide recommendations. Then we would have to act on its recommendations by manually making changes and trying to build. This is one of many examples of the power of the agentic chat, which runs commands and uses the command’s output to enrich the context of the prompt to take actions.
91
90
92
-
With the agentic coding experience, we just ask Q Developer *“Can you fix the error I am getting while building the solution? Please build and check it”*. In the following image, you will see how Q Developer runs the .NET build commands to get build errors and read the relevant files.
91
+
With the agentic coding experience, we just ask Q Developer _“Can you fix the error I am getting while building the solution? Please build and check it”_. In the following image, you will see how Q Developer runs the .NET build commands to get build errors and read the relevant files.
After it reads the files, it finds the spelling mistake and fixes it automatically. As shown in the following image, it then builds the solution to verify that its fix worked.
In the following image, Amazon Q Developer provides a summary of the error, the actions it took to build it. It even helps me with some recommendations to fix the warnings it got while running the build.
The addition of Amazon Q Developer’s agentic experience in Microsoft Visual Studio and JetBrains IDEs takes Amazon Q Developer beyond traditional chat-based interactions to intelligent, action-oriented assistance. The ability to automatically read files, generate code diffs, run shell commands, and validate changes demonstrates a level of autonomy that can significantly accelerate development tasks while maintaining code quality. The examples we’ve explored, from automated test creation to build error resolution, showcase how the agentic experience can streamline common development tasks that traditionally required multiple manual steps. This new capability, combined with multi-language support and customizable development standards, makes Amazon Q Developer a powerful ally in modern software development workflows. As development teams continue to seek ways to improve productivity without compromising code quality, Amazon Q Developer’s agentic experience represents a meaningful step forward in IDE-integrated AI assistance. Whether you’re writing tests, fixing bugs, or optimizing code, the ability to have an AI assistant that can not only suggest solutions but also implement them while maintaining context awareness is a game-changing addition to the developer’s toolkit.
111
+
The addition of Amazon Q Developer’s agentic experience in Microsoft Visual Studio and JetBrains IDEs takes Amazon Q Developer beyond traditional chat-based interactions to intelligent, action-oriented assistance. The ability to automatically read files, generate code diffs, run shell commands, and validate changes demonstrates a level of autonomy that can significantly accelerate development tasks while maintaining code quality. The examples we’ve explored, from automated test creation to build error resolution, showcase how the agentic experience can streamline common development tasks that traditionally required multiple manual steps. This new capability, combined with multi-language support and customizable development standards, makes Amazon Q Developer a powerful ally in modern software development workflows. As development teams continue to seek ways to improve productivity without compromising code quality, Amazon Q Developer’s agentic experience represents a meaningful step forward in IDE-integrated AI assistance. Whether you’re writing tests, fixing bugs, or optimizing code, the ability to have an AI assistant that can not only suggest solutions but also implement them while maintaining context awareness is a game-changing addition to the developer’s toolkit.
0 commit comments