Priority-Ordered Aspect Invocation #648
Description
Description
Providing a priority-based system for invoking aspects on a construct tree. Each aspect can specify a priority level, and the aspect invocation algorithm will ensure that higher priority aspects are applied before lower priority ones, across the entire construct tree.
Roles
| Role | User |
|---|---|
| Proposed by | @sumupitchayan |
| Author(s) | @sumupitchayan |
| API Bar Raiser | @rix0rrr @mrgrain |
| Stakeholders | @alias, @alias, @alias |
See RFC Process for details
Workflow
- Tracking issue created (label:
status/proposed) - API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
- Kick off meeting
- RFC pull request submitted (label:
status/review) - Community reach out (via Slack and/or Twitter)
- API signed-off (label
status/api-approvedapplied to pull request) - Final comments period (label:
status/final-comments-period) - Approved and merged (label:
status/approved) - Execution plan submitted (label:
status/planning) - Plan approved and merged (label:
status/implementing) - Implementation complete (label:
status/done)
Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.