-
Notifications
You must be signed in to change notification settings - Fork 680
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
removed pallet::getter
from pallet-sudo
#3370
Conversation
Signed-off-by: Matteo Muraca <[email protected]>
435e339
* master: (41 commits) Add Coretime to Westend (#3319) removed `pallet::getter` from `pallet-sudo` (#3370) gossip-support: add unittests for update authorities (#3258) [FRAME Core] remove unnecessary overrides while using derive_impl for frame_system (#3317) Update coretime-westend bootnodes (#3380) `im-online` removal cleanup: remove off-chain storage (#2290) Bump the known_good_semver group with 1 update (#3379) Fix documentation dead link (#3372) Make `sp-keystore` `no_std`-compatible and fix the `build-runtimes-polkavm` CI job (#3363) Remove unused `im-online` weights (#3373) Ensure referenda `TracksInfo` is sorted (#3325) rpc server: add rate limiting middleware (#3301) do not block finality for "disabled" disputes (#3358) fix(zombienet): docker `img` version to use in merge queues for bridges (#3337) Various nits and alignments for SP testnets found during bumping `polkadot-fellows` repo (#3359) Add broker pallet to `coretime-westend` (#3272) remove recursion limit (#3348) Update subkey README.md (#3355) Bump the known_good_semver group with 6 updates (#3347) Document LocalKeystore insert method (#3336) ...
Signed-off-by: Matteo Muraca <[email protected]>
@ggwpez the silent label was removed as I had to write a prdoc because these are breaking changes |
How is this a breaking change? |
All getters visibility is
|
Yeah, so I also first added If we are to be pedantic, they are all breaking changes. |
what should we do with this issue? |
One solution would be to just remove the usage of all getters in pallets one by one, but keep the getters. This will not be breaking change in any way, and do 99% of the work. Then, in one breaking PR, we mark the getters as deprecated and/or remove them. |
Did not realize that #3370 was indeed breaking. cc @muraca --------- Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Keeping the getter would not solve the issue, if you want to not use it. The solutions I see are either |
part of paritytech#3326 @ggwpez @kianenigma @shawntabrizi --------- Signed-off-by: Matteo Muraca <[email protected]> Co-authored-by: Kian Paimani <[email protected]>
part of #3326
@ggwpez @kianenigma @shawntabrizi