-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Hide Root
extrinsics from the normal Extrinsics UI
#1146
Comments
It doesn’t. The metadata interface does not expose any of this information. EDIT: it actually operated this way in poc-1/poc-2 before the calls interface revamp and the introduction of metadata. |
Does it make sense to have metadata expose this information? |
It can to a certain extent. Metadata v0 (first version) did have origin - which allowed you to filter out root (it was used that way with the conversion for the poc-2 version where we had private/public). It is however only a part of the puzzle -
So the existence/absence of origin is not enough, but it can get to something just based on the params. I certainly would not advocate bringing the The apps UI is the only place that I certainly deem this enum/flag useful - at the same time won't go to bat for the addition of the information since it is assumed that developers that use extrinsics in this way know what they are doing. (For all the rest there should be simple-to-follow UIs) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
If the Polkadot UI knows that a function requires
Root
origin to call, then it does not make sense to show such functions to the user in the Extrinsics UI. They should only show up in theProposals
callable function selector.The text was updated successfully, but these errors were encountered: