The purpose of the go_router for Flutter is to use declarative routes to reduce complexity, regardless of the platform you're targeting (mobile, web, desktop), handling deep linking from Android, iOS and the web while still allowing an easy-to-use developer experience.
If this moves the documentation away from the direction you want it - no worries. That said, as I was scanning that table, I was confused by the fact that Example 1 clearly stayed constant through its whole column, but Example 2 seemed to change.
If the old values for Example 2 are in fact better, I think its probably worth explaining why.
I mean for example 2 to be a path match along the way to building the entire stack as a way to show how subloc, location, path and fullpath differ at that point in the page building process.
Consistent
Example 2
in Router State sectionIf this moves the documentation away from the direction you want it - no worries. That said, as I was scanning that table, I was confused by the fact that Example 1 clearly stayed constant through its whole column, but Example 2 seemed to change.
If the old values for Example 2 are in fact better, I think its probably worth explaining why.