snapsl

Is this due to the retry feature #3623?

If I understand it correctly, the `SuccessMutationState` currently holds the updated `notifier.state`. I suggest not restricting `mutation.data` to `notifier.state`, but rather providing access to the mutated data directly. E.g. a...

> How would Riverpod know what that is? Can you elaborate? --- Benefits: 1. This could align Riverpod with Tanstack implementation for mutation 2. Direct access to mutation data ```dart...

Hopefully I get your question correctly. 😀 From an API perspective, the mutation function could return the updated todo allowing Riverpod to access it internally. ```dart @riverpod class Todos {...

This looks good to me. I don't see a way to not explicitly update the state. _Note: Should an error in a `mutation.state` automatically result in an error in `notifier.state`?_

> > Note: Should an error in a mutation.state automatically result in an error in notifier.state? > > No, I don't think that makes sense Agreed. I also do not...

@samruddhikhandale @bamurtaugh Thank you for the quick responses. I'm new to dev containers so I don't know how important dev container features are to the project. But the current state...

05/07/2024 Current list of deprecated container. (This does not include build and test status) | | maintainer | name | ociReference | workflowLastRun | repoStatus | ociStatus | repository |...

Hi, just wanted to follow up on this. Is such a feature out of scope?

That's fine. Thank you for taking the time.