4.x - Remove pathFor() and rename relativePathFor() with relativeUrlFor() #2654
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per the discussion in #2493 and the stack overflow post explaining relative/absolute
relativePathFor()
andpathFor()
are getting entirely removed from theRouteParser
component. Since this is a new interface that is the result of the fragmentation of the now deprecatedRouter
component the user will need to re-learn the new interface so no point in implementing a warning of deprecation.The
RouteParser
will now have this interface:pathFor()
relativePathFor()