[2.x] Rename NavItem fields to normalize its API #1600
Merged
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.
Changes
Makes some breaking changes to the NavItem class.
Rename protected
$destinationproperty to$routeBreaking: Rename
NavItemmethodgetDestinationtogetRouteSince the destination property in v2 is normalized to always be a route it no longer makes sense to have a divergent name for it.
Breaking: Rename
NavItemmethodisCurrenttoisActiveWhile the method is implemented by using the
currentRoutehelper, the actual end usage is to compare active state, so it makes more sense for this to use that in the name.Breaking: Rename
NavItemmethodgetGrouptogetGroupIdentifierRenames
getGroup()togetGroupIdentifier()to clarify the purpose of the method.Breaking: Rename
NavItemmethodgetLinktogetUrlRenames
getLink()togetUrl()for clarity on what the method returns.