icons: standardize on <UIcon>, drop stray <Icon> usages - #5803
Merged
Merged
Conversation
5 tasks
✅ Deploy Preview for flowfuse-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Yndira-E
enabled auto-merge
September 14, 2026 16:43
Yndira-E
disabled auto-merge
September 14, 2026 16:51
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
2 participants
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.
Description
Cleanup flagged during review of #5784 and #5792: both introduced icon usage via the bare
<Icon>component instead of Nuxt UI's<UIcon>wrapper, which the rest of the codebase already standardizes on. Functionally identical (UIconforwards its props toIcon1:1), but having both around is an avoidable inconsistency.Related Issue(s)
Checklist