-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(ec2): typo variable name "clientVpnEndoint" #13810
Comments
Great finds! If this is about released code, the proper solution would be to add a new member with the right name and add the Mind submitting a PR for that? |
Thank you for your reaction and for telling me how to fix it.It was good. ( I'll try |
Sorry, It seems that you misunderstood your intention. |
@rix0rrr @do-su-0805 If you guys don't mind shall I send a PR for this? |
@BLasan Please by all means. I'm sorry I couldn't implement it. |
I made a PR because this is not being solved. |
aws#13810 Require either clientVpnEndoint (which has a typo and is deprecated in the related PR for this issue) or clientVpnEndpoint, but not both.
aws#13810 This is to fix a linter error. The linter prefers expect and toThrow over try-catch when statements in tests are expected to throw.
aws#13810 I am only testing the logic in the constructor that makes sure only one of ClientVpnEndoint (deprecated, typo) and ClientVpnEndpoint are supplied. This commit removes setup and tests that I had copied over from another test, code that does not relate to the behavior under test.
aws#13810 We want existing usages of the deprecated prop clientVpnEndoint [sic] to still work.
aws#13810 We are deprecating the prop ClientVpnEndoint [sic] due to a typo. This commit sets up the ClientVpnRoute constructor to require one or the other of clientVpnEndoint (the deprecated name) or clientVpnEndpoint.
aws#13810 Require either clientVpnEndoint (which has a typo and is deprecated in the related PR for this issue) or clientVpnEndpoint, but not both.
aws#13810 This is to fix a linter error. The linter prefers expect and toThrow over try-catch when statements in tests are expected to throw.
aws#13810 I am only testing the logic in the constructor that makes sure only one of ClientVpnEndoint (deprecated, typo) and ClientVpnEndpoint are supplied. This commit removes setup and tests that I had copied over from another test, code that does not relate to the behavior under test.
aws#13810 We want existing usages of the deprecated prop clientVpnEndoint [sic] to still work.
aws#13810 We are deprecating the prop ClientVpnEndoint [sic] due to a typo. This commit sets up the ClientVpnRoute constructor to require one or the other of clientVpnEndoint (the deprecated name) or clientVpnEndpoint.
It is a solution to the issue #13810 Corrected the typo "clientVpnEndpoint" in the ec2 module to "clientVpnEnpoint". The maintainer (@rix0rrr) talked about @deprecated tags on existing incorrect members in the issue thread, but I didn't work on it because I thought it was an internal reference member. (if @deprecated tag is the rule of this repository in this case, please comment). This is my first commitment to this report. If there's anything wrong, please let me know in the comments. thanks ---- edit ----- Originally, this PR was #14835 , but I deleted my fork report by mistake, so I couldn't correct the error, so I uploaded it again.
It is a solution to the issue aws#13810 Corrected the typo "clientVpnEndpoint" in the ec2 module to "clientVpnEnpoint". The maintainer (@rix0rrr) talked about @deprecated tags on existing incorrect members in the issue thread, but I didn't work on it because I thought it was an internal reference member. (if @deprecated tag is the rule of this repository in this case, please comment). This is my first commitment to this report. If there's anything wrong, please let me know in the comments. thanks ---- edit ----- Originally, this PR was aws#14835 , but I deleted my fork report by mistake, so I couldn't correct the error, so I uploaded it again.
@peterwoodworth Could you please close this issue? It was resolved by PR #14902. Thanks. |
|
It is a solution to the issue aws#13810 Corrected the typo "clientVpnEndpoint" in the ec2 module to "clientVpnEnpoint". The maintainer (@rix0rrr) talked about @deprecated tags on existing incorrect members in the issue thread, but I didn't work on it because I thought it was an internal reference member. (if @deprecated tag is the rule of this repository in this case, please comment). This is my first commitment to this report. If there's anything wrong, please let me know in the comments. thanks ---- edit ----- Originally, this PR was aws#14835 , but I deleted my fork report by mistake, so I couldn't correct the error, so I uploaded it again.
❓ General Issue
The Question
variablemember name "clientVpnEndoint" in this PR feat(ec2): client vpn endpoint by jogold · Pull Request #12234 · aws/aws-cdk. Correctly "clientVpnEndpoint"Environment
Other information
P.S. Probably here too https://github.com/aws/aws-cdk/pull/12234/files#diff-53d5a35c408bb5bcd8c3b8e135dbd00660447763e9003af414536ab603d4a25dR712. Correctly "addAuthorizationRule()"
The text was updated successfully, but these errors were encountered: