-
Notifications
You must be signed in to change notification settings - Fork 721
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
Ease implementation of mock for pallets. #299
Comments
* initial commit of DummyOrdered (aka message-lane) pallet * API for relay * cargo fmt --all * some clippy + no_std * more clippy + no_std * inbound lane tests * outbound lane tests * cargo fmt --all * prune old messages whenever outbound lane is updated * do not care about MessageNonce overflow * cargo fmt --all * update crate docs * MaxHeadersToPruneAtOnce -> MaxMessagesToPruneAtOnce * MessageAction -> MessageResult * cargo fmt --all * fire MessageAccepted + MessagesDelivered * confirm message processing * cargo fmt --all * clippy * cargo fmt again * Update modules/message-lane/src/lib.rs Co-authored-by: Hernando Castano <[email protected]> * Update modules/message-lane/src/lib.rs Co-authored-by: Hernando Castano <[email protected]> * use crate::* * cargo fmt --all * Storage -> S * Update modules/message-lane/src/outbound_lane.rs Co-authored-by: Hernando Castano <[email protected]> * add method doc * Update modules/message-lane/src/inbound_lane.rs Co-authored-by: Hernando Castano <[email protected]> * added detailed module docs * Update modules/message-lane/src/lib.rs Co-authored-by: Tomasz Drwięga <[email protected]> * updated OnMessageReceived docs * prune only when new message is sent * removed #![warn(missing_docs)] * fixed merge with overlapped PR Co-authored-by: Hernando Castano <[email protected]> Co-authored-by: Tomasz Drwięga <[email protected]>
Indeed, we need this. There are too many such duplicated code. @kianenigma Could you draft a simple "task list"? Where could be the best entry point to "inject" such I'd love to take this issue. |
Option1: we can alter Second is much better as it does not involve magically generated code. |
@AurevoirXavier Are you working on it or can i try this one ? ^^ |
Aha, too many GitHub notifications.. Thank you for bringing it up! |
yeah no problem :) |
Currently there is very few provided function for doing some mocking of pallets.
People almost always implement some function like:
Those function are sometime incomplete implementation of state transition.
I think maybe we can make use of frame_executive::Executive in tests, or provide some helper to avoid having to implement those function everywhere.
The text was updated successfully, but these errors were encountered: