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
During the execution of the end-to-end tests for CSharp, the build process consistently fails with the error message: The type or namespace name 'ApiGatewayV2' does not exist in the namespace 'Amazon.CDK.AWS'. Upon further investigation, it appears that there is an issue with the namespace resolution for ApiGatewayV2 within the Amazon.CDK.AWS namespace, leading to the compilation failure.
The code generation is not aligning with the standard naming convention specified in the AWS CDK documentation for ApiGatewayV2, which suggests using Apigatewayv2 (Reference: AWS CDK Documentation).
This discrepancy raises questions regarding the consistency and compatibility across different programming languages supported by AWS CDK, such as TypeScript, Python, and Java. It is essential to investigate whether the import conventions for ApiGatewayV2 in these languages are consistent with the naming convention expected by the CSharp code generation process. If they are consistent, further analysis is needed to understand why the code generation is failing specifically for CSharp.
The text was updated successfully, but these errors were encountered:
Summary
During the execution of the end-to-end tests for CSharp, the build process consistently fails with the error message:
The type or namespace name 'ApiGatewayV2' does not exist in the namespace 'Amazon.CDK.AWS'
. Upon further investigation, it appears that there is an issue with the namespace resolution forApiGatewayV2
within theAmazon.CDK.AWS
namespace, leading to the compilation failure.The code generation is not aligning with the standard naming convention specified in the AWS CDK documentation for
ApiGatewayV2
, which suggests usingApigatewayv2
(Reference: AWS CDK Documentation).This discrepancy raises questions regarding the consistency and compatibility across different programming languages supported by AWS CDK, such as TypeScript, Python, and Java. It is essential to investigate whether the import conventions for
ApiGatewayV2
in these languages are consistent with the naming convention expected by the CSharp code generation process. If they are consistent, further analysis is needed to understand why the code generation is failing specifically for CSharp.The text was updated successfully, but these errors were encountered: