feat: access to defined scope

[nank1ro]

Allow providers to access the scope where they are defined.
This now it totally feasible

testWidgets('Test Provider.of within Provider create fn', (tester) async {
    final numberProvider = Provider((_) => 5);

    final doubleNumberProvider = Provider((context) {
      final number = numberProvider.of(context);
      return number * 2;
    });

    await tester.pumpWidget(
      MaterialApp(
        home: Scaffold(
          body: ProviderScope(
            providers: [numberProvider, doubleNumberProvider],
            child: Builder(
              builder: (context) {
                final number = numberProvider.of(context);
                final doubleNumber = doubleNumberProvider.of(context);
                return Text('$number $doubleNumber');
              },
            ),
          ),
        ),
      ),
    );
    Finder numberFinder(int value1, int value2) => find.text('$value1 $value2');
    expect(numberFinder(5, 10), findsOneWidget);
  });

This removes the boilerplate of using two nested ProviderScope widgets

[cloudflare-workers-and-pages]

Deploying flutter-disco with    Cloudflare Pages

Latest commit:	d6c4392
Status:	✅  Deploy successful!
Preview URL:	https://1aceb0b9.flutter-disco.pages.dev
Branch Preview URL:	https://feat-access-to-scope.flutter-disco.pages.dev

View logs

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

@@            Coverage Diff            @@
##              main       #17   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          215       215           
=========================================
  Hits           215       215           

Files with missing lines	Coverage Δ
...ib/src/models/providers/instantiable_provider.dart	100.00% <ø> (ø)
...kages/disco/lib/src/models/providers/provider.dart	100.00% <100.00%> (ø)
...co/lib/src/models/providers/provider_argument.dart	100.00% <100.00%> (ø)
packages/disco/lib/src/widgets/provider_scope.dart	100.00% <100.00%> (ø)

[manuel-plavsic]

I do not like the ProviderScopeState? _scopeState that is here (and the one in ArgProvider). Can we do this differently, somehow? I am confident we should keep our providers immutable.

I am pretty sure the ProviderScopeState? _scopeState introduces bugs. Remember the one we had with ArgProvider when replacing keys? I am fearing something similar here...

ProviderScope should handle the logic. If it is not possible to move it there, then I would rather close this without merging.

[nank1ro]

Because I didn't know about deactivate.
Before the problem, when the key of ProviderScope change, was that the dispose was called after initState. But deactivate is called before.

I think I can refactor the business logic again (in another PR) and make it working removing many models and keeping the logic pretty simple.

[nank1ro]

The immutability bring no value here. There are just variables with a value assigned, they are still final. (Immutable)

[nank1ro]

BTW: all tests are passing, including the key change which I tested manually

[nank1ro]

💩