-
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
IConstruct.node.addError no-op when called from an aspect #3026
Closed
1 of 5 tasks
strax opened this issue
Jun 24, 2019
· 3 comments
Β· Fixed by MechanicalRock/tech-radar#14 Β· 4 remaining pull requests
Closed
1 of 5 tasks
IConstruct.node.addError no-op when called from an aspect #3026
strax opened this issue
Jun 24, 2019
· 3 comments
Β· Fixed by MechanicalRock/tech-radar#14 Β· 4 remaining pull requests
Labels
@aws-cdk/core
Related to core CDK functionality
bug
This issue is a bug.
needs-reproduction
This issue needs reproduction.
p1
Comments
NGL321
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
@aws-cdk/core
Related to core CDK functionality
needs-reproduction
This issue needs reproduction.
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Jun 25, 2019
rix0rrr
added a commit
that referenced
this issue
Jun 28, 2019
Add an example of a validating aspect, add `Tokenization.isResolvable()` to make it easier/possible to rule out `IResolvable`s from L1 properties. Included unit tests validates that the bug reported in #3026 is not systemic.
Cannot reproduce this, wrote a unit test in linked PR in which this works as intended. |
@rix0rrr I set up a minimal repro at https://github.com/strax/cdk-3122-repro. Note that it is against 0.36, I haven't checked if |
eladb
pushed a commit
that referenced
this issue
Jun 30, 2019
Add an example of a validating aspect, add `Tokenization.isResolvable()` to make it easier/possible to rule out `IResolvable`s from L1 properties. Included unit tests validates that the bug reported in #3026 is not systemic.
This was referenced Aug 22, 2019
Closing for now. Please reopen if this is still relevant in 1.x |
This was referenced Dec 12, 2019
This was referenced Jan 20, 2020
This was referenced Sep 24, 2024
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/core
Related to core CDK functionality
bug
This issue is a bug.
needs-reproduction
This issue needs reproduction.
p1
I'm submitting a ...
What is the current behavior?
We have an aspect that we use to validate certain properties of constructs. Ideally we'd use
construct.node.addError(...)
from within the aspect to not bail at the first error. However, callingaddError
from within the aspect seems to do nothing. As a workaround, we fall back to throwing an error if the validation fails.What is the expected behavior (or behavior of feature suggested)?
IConstructNode.addError
reports an error when it is called from withinIConstruct.apply
.Please tell us about your environment:
The text was updated successfully, but these errors were encountered: