Pallets: move business logic to seperate files

[DylanVerstraete]

In lib.rs only keep:

the pallet module declaration containing:

• storage
• events
• calls
• ..

Move logic that is executed within extrinsics to seperate files. This will improve readability.

• pallet-smart-contract
• pallet-tfgrid
• pallet-dao
• pallet-burning
• pallet-kvstore
• pallet-tft-price
• pallet-validator
• substrate-validator-set
• pallet-runtime-upgrade (already good)
• pallet-tft-bridge

[renauter]

Do you think about something like this?

• lib.rs => pallet module declaration
• extr.rs => extrinsics body functions
• help.rs => helpers functions
• traits.rs => impl of some traits

[DylanVerstraete]

@renauter that is too generic, I would group functionality in files and give the file a meaningful name. For example, anything related to distribution of rewards in pallet-smart-contract -> distribution.rs

Another example, twins create/update in pallet-tfgrid -> twins.rs

[mohamedamer453]

Verified.

• pallet-smart-contract
• pallet-tfgrid
• pallet-dao
• pallet-burning
• pallet-kvstore
• pallet-tft-price
• pallet-validator
• substrate-validator-set
• pallet-runtime-upgrade (already good)
• pallet-tft-bridge

The structure of the pallets was done as mentioned.

Each pallet has its own readme.

and within each pallet in the src directory there's a file containing the implementation of each functionality.