Skip to content
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

Allow setting type of value for "Any" type in advanced transaction #213

Open
crosschainer opened this issue Jan 16, 2022 · 6 comments
Open

Comments

@crosschainer
Copy link

No description provided.

@JeffWScott
Copy link
Contributor

@Dapiguabc

The Kwargs component defaults to string when it sees "Any" as the kwarg type.

We need to think of a better way to do this.

@crosschainer do you have some suggestions?

@Dapiguabc
Copy link
Contributor

The Kwargs component will displayed as a textarea when it sees "Any" type. In my point of view, the current practice is pretty good.

@JeffWScott
Copy link
Contributor

But Any is only ever going to send string to the contract.

The point of Any is that we can send ANYTHING.

So the KWARG component should let you select the type of kwarg and then that component should be shown.

@JeffWScott
Copy link
Contributor

closed by mistake

@JeffWScott JeffWScott reopened this Mar 21, 2022
@JeffWScott
Copy link
Contributor

image

This is a mockup of how I would think it would work.

You might need to create a new ANY KWARG component to pull this off.

Also I might have missed a kwarg type in the mockup so please check

@crosschainer
Copy link
Author

The Kwargs component will displayed as a textarea when it sees "Any" type. In my point of view, the current practice is pretty good.

Its called Any type for a reason, not string

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants