-
Notifications
You must be signed in to change notification settings - Fork 6
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
Disable creation #11
Disable creation #11
Conversation
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.
Thanks 🙏
@mikiquantum would removing this extrinsic changes/breaks the metadata and makes the signer unusable? If so, I was thinking we could keep the extrinsic as is but just error out with a helpful error message and do a metadata update once we add the proxy pallet in. WDYT ? |
@vedhavyas I like that approach too, I would then create an empty extrinsic function that returns a useful error. Since I am not sure if that would affect the parity signer, although in any case, that would need to be updated with the bundle of RC3 I believe. |
@@ -2,10 +2,6 @@ | |||
# will have compiled files and executables | |||
/target/ | |||
|
|||
# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries | |||
# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html | |||
Cargo.lock |
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.
Commented multi-account creation extrinsic code.
Ensuring tests still pass by keeping the create function as internal only, for smoother transition.