[api/suggestion] CustomResource have an override for omitting CustomResourceOptions parameter
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
In the spirit of
- #410
the handwritten SDK is missing a CustomResource constructor that omits the CustomResourceOptions argument in StackReference.
Solution:
Codifying requiring CustomResource(string, CustomResourceArgs) to the abstract base classes. It would add extra safety because descendants would have to implement that method or compilation would fail.
Affected area/feature
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the handwritten Java SDK's StackReference and CustomResource constructors, then inspect the abstract base classes and their descendants. Confirm how the CustomResource(String, CustomResourceArgs) overload should be exposed without CustomResourceOptions, and verify that descendants satisfy the required constructor contract.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100