-
Notifications
You must be signed in to change notification settings - Fork 196
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
fix(compiler): panic when trying to import JSII constructs with no scope/id args #3057
Conversation
constructs with no scope/id as first arg (like some in cdktf)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Co-authored-by: Uri Bar <[email protected]>
@yoav-steinberg I think this might also resolve #1485, not totally sure |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Congrats! 🚀 This was released in Wing 0.22.23. |
See #2934
Importing a construct from JSII that doesn't have a
scope
/id
arg pair as the first constructor arguments panicked the compiler. We now detect such (unconventional) constructs and mark them as so. This makes them non compatible with ouras
/in
keywords for explicit scope/id control, but they can still be used by passing the correct (non standard) arguments to them.This resolves importing the cdktf library because its Backend constructs are an example of such non-standard constructs.
Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Monada Contribution License.