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

Upgrade to font awesome 5 #7133

Conversation

jordisala1991
Copy link
Member

Subject

I am targeting this branch, because this is BC break on 3.x.

Part of #7049

I Upgraded to font awesome 5, but keeping a compatibility layer with version 4. On this bundle I have replaced all icons with its new version, but other sonata bundles will still use the old icon names until upgraded, this ensure it will still work.

Followed this guide: https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4
And check the icon exist here: https://fontawesome.com/icons?d=gallery&p=2

I just used the 'fas' and 'fab' prefix, because thats the only "free" part, rest of icons are paid (there are some far that are not paid but not used them)

Changelog

### Changed
- Upgrade to Font Awesome 5 maintaining compatibility with version 4 icons

Use new package name for font awesome and also add a compatibility
layer with version 4, because we have a lot of icons placed around
all Sonata bundles and packages
@jordisala1991 jordisala1991 requested review from VincentLanglet and a team April 29, 2021 07:02
@jordisala1991 jordisala1991 mentioned this pull request Apr 29, 2021
31 tasks
Copy link
Member

@VincentLanglet VincentLanglet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was against the fact to update any major version (font awesome, boostrap, ...) before 4.0 because we already have a lot of BC. But since there is a BC-layer to still support font awesome 4, this seems good :)

@jordisala1991
Copy link
Member Author

I was against the fact to update any major version (font awesome, boostrap, ...) before 4.0 because we already have a lot of BC. But since there is a BC-layer to still support font awesome 4, this seems good :)

The bc layer was the trigger to me too

@VincentLanglet VincentLanglet merged commit 3c55837 into sonata-project:master Apr 29, 2021
@VincentLanglet
Copy link
Member

Thansk @jordisala1991

@jordisala1991 jordisala1991 deleted the feature/upgrade-to-font-awesome-5 branch April 29, 2021 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants