You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until #908 is fixed by dart-lang/sdk#32290, we will need to a little bit of our own type inference. I think we can do it safely in the following cases:
The Provider type is either:
ClassProvider
ExistingProvider
FactoryProvider
ValueProvider
The value of <provider>.token is an OpaqueToken<T> where T != dynamic
... we can "force" the OpaqueToken<T>'s T to be applied to Provider<T> for compilation, even though the analyzer thinks that T of Provider<T> is dynamic due to the SDK bug above.
That should be enough to unblock #908, and not cause any regressions.
Until #908 is fixed by dart-lang/sdk#32290, we will need to a little bit of our own type inference. I think we can do it safely in the following cases:
Providertype is either:ClassProviderExistingProviderFactoryProviderValueProvider<provider>.tokenis anOpaqueToken<T>whereT != dynamic... we can "force" the
OpaqueToken<T>'sTto be applied toProvider<T>for compilation, even though the analyzer thinks thatTofProvider<T>is dynamic due to the SDK bug above.That should be enough to unblock #908, and not cause any regressions.