This is macro hygiene related to #4 ; the error message when a user does not include a dependency required in the macros can be improved through this issue.
The solution is to include all required dependencies in this crate. So instead of
// inside macro
construct_runtime!
it is better to include frame_support as a dependency in this crate's Cargo.toml and call it like this:
This is done in #1 for frame_support::construct_runtime and sp_api::iml_runtime_api macros but is not done for all the other pallet dependencies required. This issue exists to add all of those.
This is macro hygiene related to #4 ; the error message when a user does not include a dependency required in the macros can be improved through this issue.
The solution is to include all required dependencies in this crate. So instead of
it is better to include
frame_supportas a dependency in this crate's Cargo.toml and call it like this:This is done in #1 for
frame_support::construct_runtimeandsp_api::iml_runtime_apimacros but is not done for all the other pallet dependencies required. This issue exists to add all of those.