Hi @ghaith-abtah-5
As mentioned in Migration guide, you can work around this by following code (it is not guaranteed to work in later versions, though)

GoRouter _router;
final String location = _router.routerDelegate.currentConfiguration.uri.toString();
final bool canPop = _router.routerDelegate.canPop;

Please let us know your opinion if it applies to your case or not.

Thanks for reply.
I cannot relay on this method because of "it is not guaranteed to work in later versions", and there was no warning or deprecation annotation that you are going to remove the location property.
As I said, I can try to save the current route and implement this on my own but it will take time and effort.
What is the reason that it was removed without any warning?

Hi @ghaith-abtah-5,
The Migration guide has been updated after 9.0.2, you can try below sample migration code:

final RouteMatch lastMatch = _router.routerDelegate.currentConfiguration.last;
final RouteMatchList matchList = lastMatch is ImperativeRouteMatch ? lastMatch.matches : _router.routerDelegate.currentConfiguration;
final String location = matchList.uri.toString();

there was no warning or deprecation annotation that you are going to remove the location property.

Even though this is announced in the Changelog (this is a breaking change since 9.0.0), it should be warned in the API documentation. Thanks!

Thanks @huycozy for the clarification.
I still didn't get the reason why you have made this change where a lot of developers use the location propriety the old way but maybe they didn't notice the change yet and now we can get it in three lines of code instead of one simple line.

The reason we remove the location is to avoid people looking up GoRouter.of(context).location since it will not rebuild the widget if it changes.

but i agree the current workaround is ugly

Here is a crazy idea. How about we have a method named 'location' that implements this workaround, then we don't have any breaking changes. Once we have a proper alternative solution then remove this location method.

Inspired by @chrisdlangham 's idea I have created this:

extension GoRouterExtension on GoRouter {
  String location() {
    final RouteMatch lastMatch = routerDelegate.currentConfiguration.last;
    final RouteMatchList matchList = lastMatch is ImperativeRouteMatch ? lastMatch.matches : routerDelegate.currentConfiguration;
    final String location = matchList.uri.toString();
    return location;
  }
}

for anyone else to use it. Just simply use it like this:

GoRouter.of(context).location()

Inspired by @chrisdlangham 's idea I have created this:

extension GoRouterExtension on GoRouter {
  String location() {
    final RouteMatch lastMatch = routerDelegate.currentConfiguration.last;
    final RouteMatchList matchList = lastMatch is ImperativeRouteMatch ? lastMatch.matches : routerDelegate.currentConfiguration;
    final String location = matchList.uri.toString();
    return location;
  }
}

for anyone else to use it. Just simply use it like this:

GoRouter.of(context).location()

make it a property and you are golden:

extension GoRouterLocation on GoRouter {
  String get location {
    final RouteMatch lastMatch = routerDelegate.currentConfiguration.last;
    final RouteMatchList matchList = lastMatch is ImperativeRouteMatch
        ? lastMatch.matches
        : routerDelegate.currentConfiguration;
    return matchList.uri.toString();
  }
}

Can I somehow get the access to parameters sent to current route?

alright I will just add a getter to get routeMatchList in GoRouter. Though this is not critical as there is work around, but it is getting quite annoying when developing an app

Inspired by @chrisdlangham 's idea I have created this:

extension GoRouterExtension on GoRouter {
  String location() {
    final RouteMatch lastMatch = routerDelegate.currentConfiguration.last;
    final RouteMatchList matchList = lastMatch is ImperativeRouteMatch ? lastMatch.matches : routerDelegate.currentConfiguration;
    final String location = matchList.uri.toString();
    return location;
  }
}

for anyone else to use it. Just simply use it like this:

GoRouter.of(context).location()

make it a property and you are golden:

extension GoRouterLocation on GoRouter {
  String get location {
    final RouteMatch lastMatch = routerDelegate.currentConfiguration.last;
    final RouteMatchList matchList = lastMatch is ImperativeRouteMatch
        ? lastMatch.matches
        : routerDelegate.currentConfiguration;
    return matchList.uri.toString();
  }
}

there is problem with the above approach as it seems the getter,

  /// The last matching route.
  RouteMatch get last => matches.last;

getter last tries to get the last element which likely be empty Array and so would return the error

Also, this issue very likely seems to cause the issue, #116855

will shared my code, which actually preventing that from happening issue...

is it me or when I use this new way to get current location, it shows instead the previous location and not the current one ?... Is anyone having the same issue ?

is it me or when I use this new way to get current location, it shows instead the previous location and not the current one ?... Is anyone having the same issue ?

Nope nope, actually it does current location.

is it me or when I use this new way to get current location, it shows instead the previous location and not the current one ?... Is anyone having the same issue ?

Yes, if I use context.push instead of context.go the _router.routerDelegate.currentConfiguration.uri shows the previous location. I've switched to using context.go and it works now. If you previously awaited the push method's completion to do further work consider using GoRoute's onExit callback instead.

Possibly related: #132930

This issue is assigned to @chunhtai but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

This issue was assigned to @chunhtai but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

is it me or when I use this new way to get current location, it shows instead the previous location and not the current one ?... Is anyone having the same issue ?

For me, it is rebuilding all the routes that were previously injected in the stack (im using context.push to navigate). This might just be me though, as all the pages in my project have the same path: /:param1/:param2

I fetch additional data, via api call, based on the params and show content according to the response on the page. If I use context.go, everything works fine.

The reason I need to use context.push is to support back button presses on mobile. I found a related issue, that was seemingly, resolved in previous versions. I dont know if its the same bug. I solved the issue by adding the following code (which I found in a comment on the previous issue I mentioned):

Minimum code:

extension GoRouterLocation on GoRouter {
  String get location {
    final RouteMatch lastMatch = routerDelegate.currentConfiguration.last;
    final RouteMatchList matchList = lastMatch is ImperativeRouteMatch
        ? lastMatch.matches
        : routerDelegate.currentConfiguration;
    return matchList.uri.toString();
  }
}

// in the route list ->
GoRoute(
      path: '/:num',
      builder: (context, state) {
        if (state.matchedLocation != GoRouter.of(context).location) {
          return const SizedBox.shrink();
        }

        context.read<AppBloc>().add(Reload(url: state.pathParameters['num']!)); // api call

        return const Renderer();
      },
    )

Here is the link to the comment: #123570 (comment)

I was happy with Vrouter but it's dependencies not being updated in two years just broke my app.

Vrouters ability to get the current url was nicer tbh

selected: (context.vRouter.url == "my_url"),

I was happy with Vrouter but it's dependencies not being updated in two years just broke my app.

Vrouters ability to get the current url was nicer tbh

selected: (context.vRouter.url == "my_url"),

I thought the point was NOT to use context