Read original `Provider` from `Override` about riverpod

[rrousselGit]

Why are you overriding "name" as "emphasis"?

[jimmy-robert]

Why not? 🙂 It is just a simple example here, but there can be cases where I want to override a behavior to add some features but still calling the original provider (e.g: modify a real HTTP response, transform a value, ...).

I think I would use this for mocks but it can still be used for real use cases I guess.

[rrousselGit]

For sure. I'm just trying to understand the use-case as much as possible.
To make sure that there isn't a different solution that we could take

[rrousselGit]

Note that you could do it with two providers:

final provider = Provider((ref) => 'Foo');
final originalProvider = Provider((ref) => ref.read(provider).value);

So when you override provider, originalProvider is still not overriden

ProviderScope(
  overrides: [
    provider.overrideAs(Provider((ref) {
      final original = ref.read(originalProvider).value;
      return 'Hello $original';
   }),
  ],
  child: // 
)

[tbm98]

I think use-case of overrideAs is for testing and both of them should be unrelated to each other.

[rrousselGit]

Closing for now as I don't think this is truly needed since there are other solutions, and implementing that would decrease overall performances.