Skip to content

eslint rules for CDK apps #32293

Open
Open
@rix0rrr

Description

Describe the feature

We should have a collection of linter rules to help write CDK apps. There are common mistakes that are hard to prevent at runtime, and require static source analysis.

Examples:

  • Don't use variable names in construct IDs
  • Don't mix L1 and L2 types
  • Don't pass scope but pass this

Etc. I'm sure we can come up with more. Put your best ideas in here!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort/mediumMedium work item – several days of effortfeature-requestA feature should be added or improved.p1package/toolsRelated to AWS CDK Tools or CLI

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions