-
Notifications
You must be signed in to change notification settings - Fork 246
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
bug(go): Using Aspects causes panic: Call using *awscdk.IConstruct as type awscdk.IConstruct #2793
Comments
@all-contributors add @corymhall for bug |
I've put up a pull request to add @corymhall! 🎉 |
Thanks for reporting this! I have been able to reproduce this, and have identified a fix for that. I'll submit a PR shortly (a draft, though - as I still have to write a test that covers the previously broken case). |
The callback handling logic was incorrectly handling "pure" interface parameters. The reflection piece would create a new argument value in preparation for the callback, however for interfaces, it would leave the pointer to the interface type (as returned by `reflect.New`) instead of indirecting to the interface itself as appropriate. Fixes #2793
The callback handling logic was incorrectly handling "pure" interface parameters. The reflection piece would create a new argument value in preparation for the callback, however for interfaces, it would leave the pointer to the interface type (as returned by `reflect.New`) instead of indirecting to the interface itself as appropriate. Fixes #2793
The callback handling logic was incorrectly handling "pure" interface parameters. The reflection piece would create a new argument value in preparation for the callback, however for interfaces, it would leave the pointer to the interface type (as returned by `reflect.New`) instead of indirecting to the interface itself as appropriate. Fixes #2793
The callback handling logic was incorrectly handling "pure" interface parameters. The reflection piece would create a new argument value in preparation for the callback, however for interfaces, it would leave the pointer to the interface type (as returned by `reflect.New`) instead of indirecting to the interface itself as appropriate. Fixes #2793
The callback handling logic was incorrectly handling "pure" interface parameters. The reflection piece would create a new argument value in preparation for the callback, however for interfaces, it would leave the pointer to the interface type (as returned by `reflect.New`) instead of indirecting to the interface itself as appropriate. Fixes #2793 --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
|
Adds @corymhall as a contributor for bug. This was requested by RomainMuller [in this comment](#2793 (comment))
🐛 Bug Report
Affected Languages
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)Go
General Information
What is the problem?
I am trying to use Aspects with the go CDK and I get the below error when running synth:
I was able to reproduce the issue with the default app that is created via
cdk init --language=go app
Here is my code:
Verbose Log
The text was updated successfully, but these errors were encountered: