Skip to content

useMultiMutation() mutation on list views #88

@posva

Description

@posva

When using a regular useMutation() within a list view, you can mutate different entities but you only get access to the loading state of the last one. It would be useful to allow a version that requires a key to compute the different properties in a Map and then each value becomes a function instead of a computed: data(key), isLoading(key) so we can check the progress

Problems:

  • How long should each data be preserved
  • Should there be a way to remove the data
  • Any difference between errors and successes?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions