update tasks funding mechanism #1018
Conversation
| //!- **Description**: Fund the `recv_msg` operation from the caller account. | ||
| //!- **Specification**: Ensure that the cost for the `recv_msg` operation is covered by the caller, similar to `register_gateway` and `submit_result`. The caller is the root and shard member in the cases of `register_gateway` and `submit_result`, respectively. | ||
| //! | ||
| //!## Not Feature: Estimations of Required Funds |
There was a problem hiding this comment.
this looks like it should be an issue, not organized in the crate-level docs IMO
There was a problem hiding this comment.
We plan to include a section for planned features in docs and after that, these can be picked to create issues based on development priority.
There was a problem hiding this comment.
these should start as issues and be turned into docs only after the implementation
| @@ -39,6 +39,59 @@ | |||
| //! number of tasks to be reset is reached. | |||
| #![doc = simple_mermaid::mermaid!("../docs/reset_tasks.mmd")] | |||
|
|
|||
| //!## Future Features | |||
There was a problem hiding this comment.
shouldn't these all be issues? I don't see the value of adding planned features with planned specs to the crate-level docs?
|
agree with amar. think this would be better as github issues. |
|
Closing this and opening issues with the content as commented on above. After we implement it & merge the implementation, @taniasaleem can add crate-level docs describing it as it is implemented |
Description
This provides the updates that need to be done in the tasks pallet regarding the task funding.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
Code review prechecks: