Pallet-level Dispatch

We want to make our code more modular and extensible.

Currently, dispatch happens through the RuntimeCall, which is hardcoding dispatch logic for each of the Pallets in our system.

What we would prefer is for pallet-level dispatch logic to live in the Pallet itself, and our Runtime to take advantage of that. We have already seen end-to-end what it takes to set up call dispatch, so let’s do it again at the Pallet level.

Pallet Call

To make our system more extensible, we want to keep all the calls for a pallet defined at the pallet level.

For this, we define an enum Call in our Balances pallet, and just like before, we introduce a new enum variant representing the function that we want to call.

Note that this enum needs to be generic over T: Config because we need access to the types defined by our configuration trait!

Pallet Dispatch

You will also notice in the template, we have included the shell for you to implement pallet-level dispatch.

Everything should look the same as the runtime-level dispatch, except the type Call is the pallet-level call we just created.

Just like before, you simply need to match the Call variant with the appropriate function, and pass the parameters needed by the function.

Create Your Pallet-level Dispatch

Follow the TODOs in the template to complete the logic for pallet-level dispatch.

The “never constructed” warning for the Transfer variant is okay.

In the next step, we will use this logic to improve our dispatch logic in our Runtime.