-
Notifications
You must be signed in to change notification settings - Fork 690
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
Expose types from sc-service
#5855
base: master
Are you sure you want to change the base?
Conversation
sc-service
This feature should not exist at all... Could you give some more details on how you implemented this? I mean why do you need to expose these types at all? I would say that you only need to write some |
We had to change the |
Which validation? Could you be more specific? |
Description
At moonbeam we have worked on a
lazy-loading
feature which is a client mode that forks a live parachain and fetches its state on-demand, we have been able to do this by duplicating some code fromsc_service::client
. The objective of this PR is to simplify the implementation by making public some types in polkadot-sdk.sc_service::client
I do not see a point to only expose this type whentest-helpers
feature is enabledsc_service::client::WasmOverride
sc_service::client::WasmSubstitutes
sc_service::client::CodeProvider
Required after Unifycode_at
logic betweenCallExecutor
&Client
#4618In my opinion the advantages of making these types public is greater than keeping them as internals, since it gives more flexibility to devs when building their parachain clients.
Integration
Not applicable, the PR just makes some types public.
Review Notes
The changes included in this PR give more flexibility for client developers by exposing important types.