(core): standardize naming of integration classes
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
Integration class names are pretty much all over the place right now, a review.
## Events Targets
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_events_targets-readme.html
```
+
```

## StepFunctions
```
MOSTLY: + +
Sometimes: + +
Legacy: +
```
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_stepfunctions_tasks-readme.html

## CodePipeline Actions
```
+ + + "Action"
```

## SNS Subscriptions
```
+ "Subscription"
```

## CloudWatch Actions
```
+ "Action"
```

## AutoScaling HookTargets
```
+ "Hook"
```

## GlobalAccelerator Endpoints
```
+ "Endpoint"
```

Contributor guide
Research direction
Start by reviewing the integration class names in the Events Targets, StepFunctions, CodePipeline Actions, SNS Subscriptions, CloudWatch Actions, AutoScaling HookTargets, and GlobalAccelerator Endpoints areas named in the issue. Compare them with the listed naming patterns and determine the consistent convention and affected public names; done means the naming review has a documented decision covering all listed areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- developer-experience, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100