Skip to content

Allow frame-macros to work without needing frame-support, frame-system and such being in scope.  #173

Closed
@kianenigma

Description

I am playing with the idea of having a single crate, called frame, that is only docs + re-exports of the major types that you need when developing with frame, hopefully removing the need to import like 6 crates just have a shell pallet.

One blocker I have so far is that pallet macros currently make an assumption about the existence of frame-system, frame-support, codec, and type-info in Cargo.toml. In principle, I don't think this dependency is strictly needed, and end of the day the pallet macros need to have a valid path to these crates, eg in the simplest case #[pallet::pallet(<path-to-system>, <path-to-support>)], but I am wondering if there is a beter way to handle that?

Before investigating further, I should bring in this frame examples as a branch.

Metadata

Assignees

No one assigned

    Labels

    C1-mentorA task where a mentor is available. Please indicate in the issue who the mentor could be.I5-enhancementAn additional feature request.T1-FRAMEThis PR/Issue is related to core FRAME, the framework.

    Type

    No type

    Projects

    • Status

      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions