-
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
fix(python): correctly handle interface declarations on returned objects #980
Conversation
When the returned type had a known base type, the interfaces tagged on the object reference tag. This addresses this problem.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
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.
I am wondering if we should add tests for .NET and Java just in case.
- implement the test for #976 in Java and .NET (PASSED) - port `canLeverageIndirectInterfacePolymorphsm` to python (PASSED)
@RomainMuller I tool the liberty of implementing this test in .NET and Java, just in case, and also noticed that a related test is missing from python, so I added it (all passed). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
using 'Resource' object has no attribute ... error still exists. |
@dxunix I had to update all of the Python dependencies in my virtual env before the issue was resolved. |
When the returned type had a known base type, the interfaces tagged on the object
reference tag. This addresses this problem.
Fixes #976
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.