Migration issues V6 to V7

[burekas7]

Hi,

I'm looking in the guide:
https://modular.flutterando.com.br/docs/flutter_modular/migration/

But don't find answers for:

MaterialApp.router(
            routerDelegate: Modular.routerDelegate,   <====== Error
            routeInformationParser: Modular.routeInformationParser, <====== Error

2. Consumer is used both in Provider package and Modular:

The name 'Consumer' is defined in the libraries
'package:flutter_modular/src/state/consumer.dart (via package:flutter_modular/flutter_modular.dart)' 
and 
'package:provider/src/consumer.dart (via package:provider/provider.dart)'.

3. What about:

pushReplacementNamed
popUntil

4. And this one:

navigateHistory

[jacobaraujo7]

Hello!

Of these, only navigatehistory was in fact removed because it doesn't seem like a correct use, since browsers already keep this history and apps usually don't care about it.

In fact, the Consumer is the same as the Provider, even with the provide property of the route it is not necessary to use the Provider package, since the modular directly replaces.

The push and pop names are the same as Navigator

Looking here some things have to be improved in migration. Can you do this for us?

[PhillDubois]

Hi, in my app I needed the navigateHistory to determine from witch location the user arrived at a certain page. Is there a way to quickly now that ?
Example:
User was in /home -> /screenA -> screenX or /home -> /screenB -> screenX. If on my history I had /screenA I would display a message, otherwise not. I know I could pass an argument to the page with this information, but I wanted to preserve the main logic so in the future if there are other flows and devs forget this, they don't break the functionality.