-
Notifications
You must be signed in to change notification settings - Fork 89
feat: replace FontAwesome with Lucide icons #589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tarunsinghofficial
wants to merge
7
commits into
develop
Choose a base branch
from
feat/fontawsome-lucide-migration
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
69e8387
chore: swap FontAwesome for Lucide packages
tarunsinghofficial d0a732d
feat: use Lucide icons and remove FontAwesome icons from whole app
tarunsinghofficial b541959
feat: remove FA chevronup direction icon and inline SVG
tarunsinghofficial 6acbd5d
chore: merge develop and migrate SurveyBanner, TripPlan to Lucide
tarunsinghofficial 77b68b1
fix: prettier formatting and add rotate-rtl to directional icons
tarunsinghofficial cb67aa4
fix: restore direction caret box size and unify recents icon
tarunsinghofficial c3ac90c
fix: bump svelte to 5.16.0 so Lucide array class prop renders correctly
tarunsinghofficial File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dropping
@fortawesome/*here is now a build break against currentdevelop, because #585 landed after this branch was last pushed and brought six new files that import it:That's my fault for merging #585 first without waiting on your answer about ordering. Merge
developin and convert those six the same way as the other 35 — the components want Lucide'sStar(it takesfillthe same way, so the filled/unfilled toggle carries over), and the tests should slot into theLucideStub.sveltemock you already built.