Move UINavigationItem extensions to new FluentNavigationItemConfiguration#2179
Merged
mischreiber merged 3 commits intomicrosoft:mainfrom Jun 13, 2025
Merged
Conversation
laminesm
approved these changes
Jun 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Platforms Impacted
Description of changes
Second pass at addressing #2177. In order to avoid potential conflicts and confusion, this breaking change removes all extended UINavigationItem properties and places them onto a single configuration object, the
FluentNavigationItemConfigurationclass. This removes the conflict withsubtitle.However, now that we know this new property is coming, this change also builds fallbacks to handle the existence of
UINavigationItem.subtitle, and to prefer it to the existing Fluent value. This is done with a few changes:subtitledeprecated on iOS/visionOS/macCatalyst 26+Verification
Confirmed expected behavior across iOS 18 and 26, using both Xcode 16.4 and 26.0b1.
Visual Verification
Pull request checklist
This PR has considered:
Microsoft Reviewers: Open in CodeFlow