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
It's sometimes useful to access the pathDef for a route, such as when logging which route is getting executed. In the code, there are two different ways that the path definition is referenced:
The places you mentioned in the same place right? 2nd one using the 1st one.
Anyway, I get it.
In the route, you want to mention it as pathDef. Yep, which is sounds good to me.
But, I don't wanna break any apps. So, we need to keep the path as it is.
We can remove path in 3.0
It's sometimes useful to access the pathDef for a route, such as when logging which route is getting executed. In the code, there are two different ways that the path definition is referenced:
Would you be open to a PR which standardized on pathDef?
It would help make things like this more clear:
The text was updated successfully, but these errors were encountered: