-
Notifications
You must be signed in to change notification settings - Fork 443
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
Generate metadata for constructor return type #1460
Changes from all commits
4be003b
68df576
ced904f
1686a8a
42fac54
7e4aed2
2912089
bdd717f
32e99fa
f5ec420
4959e4c
e59821f
e335081
17795d0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,7 +68,7 @@ where | |
&Contract::KEY, | ||
contract, | ||
); | ||
Ok(()) | ||
ink_env::return_value(ReturnFlags::default().set_reverted(false), &()); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. But what if the return type is I suppose you have not been able to test this since there are no clients which are attempting to decode the return value? One way to test it would be via the in-contract instantiation with |
||
} | ||
Err(error) => { | ||
// Constructor is fallible and failed. | ||
|
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.
It's not a great way to test it using strings like this. It's brittle and dependent upon the codegen impl.
If we can come up with a good solution with types + reflection this will be easier to test.