-
Notifications
You must be signed in to change notification settings - Fork 684
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
[FRAME] Pallet storage items should be public #3787
Comments
Good pick up, yeah I can't think of a good reason for storage to ever be private/inaccessible. |
There might be a few instances where we want to restrict direct access to the underlying storage and instead only allow the public APIs to modify it. For example, something like One of the motivations for pallet splitting work was to make this encapsulation better, but making these public by default would take us even farther. Can we only make these public for tests if that's the primary reason here? |
Tests and benchmarks, yes. I guess we could just modify the visibility for those features? |
Hello @ggwpez is there an instance of this? |
I think we went with just making all storage items pub, no need to shield them. |
Actually going to close in favour of #3326 |
Since we are removing getters, it would be useful to make the storage items of all pallets public.
Otherwise it is not easily possible to test stuff where accessing another pallets' storage would be useful.
I guess we could issue a warning on private storage items, but maybe that is too opinionated for everyone.
The text was updated successfully, but these errors were encountered: