-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: Support generics on messages
attribute in main contract
call
#238
feat: Support generics on messages
attribute in main contract
call
#238
Conversation
8470f7f
to
9a0ac19
Compare
4e37906
to
04e0edd
Compare
Codecov Report
@@ Coverage Diff @@
## feat/generics_support #238 +/- ##
=========================================================
- Coverage 88.36% 88.29% -0.08%
=========================================================
Files 25 25
Lines 1444 1478 +34
=========================================================
+ Hits 1276 1305 +29
- Misses 168 173 +5
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
6dc3bc6
to
629f3a2
Compare
04e0edd
to
fd40f3d
Compare
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.
Seems mostly good, but I missed some tests. What happens if I try to implement the same interface twice with different generics? I think it should fail due to name collision. Also - can the contract itself be generic at this point? I believe not, right?
One thing I really miss is the tests of multitest utilities generated.
I tested it with some more interfaces in this PR #239. Yes you cannot implement same interface twice due to name collisions. |
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.
With your explanations - LGTM
close #226