Skip to content
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

Quick fix to use Sharp Icons #261

Merged
merged 2 commits into from
Nov 3, 2024

Conversation

JudahMcNicholl
Copy link
Contributor

--Assuming you have set up Pro--
Copy the contents of icon-families.json into the lib/fonts/icons.json

This code is backwards compatible so that if you use icons.json it will pull out the relevant fields.
icon-families.json doesn't have the styles tag so instead we can iterate over the svgs keys of "classic" and check if it has "sharp"
This also means that the key for sharp is now "sharp <thin, light, regular, solid> name"
so we have to do some manipulation to remove the empty space to map the Class names correctly and to un-comment out the relevant pubspec.yaml files.

I hope this helps someone out to start using Sharp Icons in this.

--Assuming you have set up Pro--
Copy the contents of icon-families.json into the lib/fonts/icons.json

This code is backwards compatible so that if you use icons.json it will pull out the relevant fields.
icon-families.json doesn't have the styles tag so instead we can iterate over the svgs keys of "classic" and check if it has "sharp"
This also means that the key for sharp is now "sharp <thin, light, regular, solid> name"
so we have to do some manipulation to remove the empty space to map the Class names correctly and to un-comment out the relevant pubspec.yaml files.

I hope this helps someone out to start using Sharp Icons in this.
@matheusbristot
Copy link

works fine!!!

@michaelspiss michaelspiss merged commit abc02ce into fluttercommunity:master Nov 3, 2024
@michaelspiss
Copy link
Collaborator

Thanks @JudahMcNicholl for putting the time into this and providing this pull request. Much appreciated! Also thanks to @matheusbristot for verifying the solution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants