You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
gui1117 opened this issue
May 3, 2021
· 2 comments
· Fixed by #10650
Labels
Z1-easyCan be fixed primarily by duplicating and adapting code by an intermediate coderZ6-mentorAn easy task where a mentor is available. Please indicate in the issue who the mentor could be.
@bkchr proposed removing all on_runtime_upgrade logic from the pallets and handling it directly at the runtime level, which seems like a good option imo. That way a team can check the references and order however they please.
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions.
stalebot
added
the
A5-stale
Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
label
Jul 7, 2021
I really agree with this. Handling migrations that are baked into the pallet is too opaque in my opinion.
stalebot
removed
the
A5-stale
Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
label
Sep 17, 2021
gui1117
added
Z1-easy
Can be fixed primarily by duplicating and adapting code by an intermediate coder
Z6-mentor
An easy task where a mentor is available. Please indicate in the issue who the mentor could be.
labels
Sep 20, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Z1-easyCan be fixed primarily by duplicating and adapting code by an intermediate coderZ6-mentorAn easy task where a mentor is available. Please indicate in the issue who the mentor could be.
@bkchr proposed removing all
on_runtime_upgrade
logic from the pallets and handling it directly at the runtime level, which seems like a good option imo. That way a team can check the references and order however they please.Originally posted by @drewstone in #8683 (comment)
Some hint for implementers:
That should be all I think.
The text was updated successfully, but these errors were encountered: