-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(cli): Python id
parameter in init template conflicts with built-in
#10874
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This id is more generic though. I don't think stack_id
is the best name to start giving people mental models. construct_id
would be better, or cid
if construct_id
is too long to type.
@@ -1,9 +1,9 @@ | |||
from aws_cdk import core | |||
|
|||
|
|||
class %name.PascalCased%Stack(core.Stack): | |||
class % name.PascalCased % Stack(core.Stack): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These autoformats are going to break things I believe.
id
parameter conflicts with built-in
id
parameter conflicts with built-inid
parameter in init template conflicts with built-in
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
In Python,
id()
is a builtin function that can cause linter warnings and some confusion while developing stacks in Python. This change simply renamesid
tostack_id
in the init template.