Skip to content

[4.2] Remove the SCSS deprecations - #36906

Closed
dgrammatiko wants to merge 33 commits into
joomla:4.2-devfrom
dgrammatiko:4.1-dev-fix-scss-div
Closed

[4.2] Remove the SCSS deprecations#36906
dgrammatiko wants to merge 33 commits into
joomla:4.2-devfrom
dgrammatiko:4.1-dev-fix-scss-div

Conversation

@dgrammatiko

@dgrammatiko dgrammatiko commented Jan 31, 2022

Copy link
Copy Markdown
Contributor

Pull Request for Issue # .

Summary of Changes

  • Removing the math.div deprecations from the scss compiler
  • update Font Awesome to v6
  • update choices.js to v10

Testing Instructions

  • Apply this Pr's branch
  • run npm ci
  • Check that nothing is broken visually

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Documentation Changes Required

@joomla-cms-bot joomla-cms-bot added NPM Resource Changed This Pull Request can't be tested by Patchtester PR-4.1-dev labels Jan 31, 2022
@dgrammatiko dgrammatiko closed this Feb 1, 2022
@dgrammatiko
dgrammatiko deleted the 4.1-dev-fix-scss-div branch February 1, 2022 12:52
@dgrammatiko
dgrammatiko restored the 4.1-dev-fix-scss-div branch February 10, 2022 13:40
@dgrammatiko dgrammatiko reopened this Feb 10, 2022
@dgrammatiko dgrammatiko changed the title [skip] Nothing to see here [4.1.x] Remove the SCSS deprecations Feb 10, 2022
@HarshJaiswani

Copy link
Copy Markdown

I have tested this item ✅ successfully on bcc3ce8


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/36906.

Comment thread package-lock.json Outdated
"version": "5.65.1",
"resolved": "https://registry.npmjs.org/codemirror/-/codemirror-5.65.1.tgz",
"integrity": "sha512-s6aac+DD+4O2u1aBmdxhB7yz2XU7tG3snOyQ05Kxifahz7hoxnfxIRHxiCSEv3TUC38dIVH8G+lZH9UWSfGQxA=="
"version": "5.64.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this should be 5.65.1

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done, btw not reflecting the actual version in the package.json is the source of those inconsistencies...

# Conflicts:
#	package-lock.json
@roland-d

roland-d commented Mar 9, 2022

Copy link
Copy Markdown
Contributor

@dgrammatiko I sent you a PR to fix the conflict, after that I can merge this PR. Thank you.

@dgrammatiko

dgrammatiko commented Mar 9, 2022

Copy link
Copy Markdown
Contributor Author

after that I can merge this PR

About merging this PR: @brianteeman already spotted some visual changes due to the upgrade to v6 of Font Awesome. This might need some research (it's just comparing the font icon names using the 2 different sites v5 and v6, making some notes and then maybe figure out if some other mapping is making more sense for the current use case, it's a bit of work...)

It would be nice to roll an article that 4.2 will use FA v6 and ask devs to adjust (early) their code eg from:

font-family: "Font Awesome 5 Free";

to

font-family: "Font Awesome 6 Free","Font Awesome 5 Free";

Also this is the only part that needs to be documented

@Quy

Quy commented Mar 9, 2022

Copy link
Copy Markdown
Contributor

Please merge. I noticed it too, however, this can be done in separate PR which I can do.

@roland-d

roland-d commented Mar 9, 2022

Copy link
Copy Markdown
Contributor

Thank you @Quy I am just waiting for Drone and AppVeyor to finish.

@dgrammatiko

Copy link
Copy Markdown
Contributor Author

@roland-d do you want me to do some back port of this to 4.1 (without the FA v6) or someone already on it?

@brianteeman

Copy link
Copy Markdown
Contributor

do/should we really be updating fontawesome? \they are breaking changes AND fs5 is designated LTS

@dgrammatiko

Copy link
Copy Markdown
Contributor Author

do/should we really be updating fontawesome? \they are breaking changes AND fs5 is designated LTS

FA v5 still has the deprecated div notifications and there is not update but also it's not the end of the world we could override some values locally and fix it in this repo if there's no fix upstream. Anyways, not my decision, I could redo this with the v5...

@brianteeman

Copy link
Copy Markdown
Contributor

the deprecated div notifications
which are not seen by the user

@dgrammatiko

Copy link
Copy Markdown
Contributor Author

which are not seen by the user

True, but it's annoying for devs (not really a reason) and might be a problem for new contributors (not really, if there was a nice welcoming DX)
Also there's no documentation that states that the node audit/deprecations/etc are irrelevant for the distributed product

FWIW this PR's intention was to just fix the math div deprecations, the FA upgrade shouldn't be part of this. Probably I was too fast to jump on the newest-greatest train without thinking too much. I'll try to do a PR in the 4.1 with only the needed changes and close this. If there's a decision to go with v6, diffing the changes here and making a new pr should be a 5min job...

@brianteeman

Copy link
Copy Markdown
Contributor

agreed

@brianteeman

Copy link
Copy Markdown
Contributor

and 6,1 comes out next week

@dgrammatiko

Copy link
Copy Markdown
Contributor Author

OK closing here the PR for 4.1 is here: #37243

If anyone still wants to upgrade to FA v6 the code is here

@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Mar 10, 2022
@dgrammatiko
dgrammatiko deleted the 4.1-dev-fix-scss-div branch March 12, 2022 14:47
@joomleb

joomleb commented May 22, 2022

Copy link
Copy Markdown

Hi guys,
sorry,I did not understand. At the end FA6 will not be included into the J4.1, right ?
But, Will it be added in J4.2 ?

@roland-d

Copy link
Copy Markdown
Contributor

Hello,

This will not be in Joomla 4.2 nor do I know when it will come.

@HDInfautre

HDInfautre commented Sep 13, 2022

Copy link
Copy Markdown

Hi
There are lots of new icons Font Awesome v6 :-)
Do you know when this can be integrated? 4.2.3 ?
or what is the method to integrate it now ? if there is no date

@HLeithner

Copy link
Copy Markdown
Member

Font Awesome icon packs are not backward compatible, so upgrading them would break other websites. if we upgrade it, it's
likely to be in Joomla 5.0.

@HDInfautre

HDInfautre commented Sep 13, 2022

Copy link
Copy Markdown

Font Awesome icon packs are not backward compatible, so upgrading them would break other websites. if we upgrade it, it's likely to be in Joomla 5.0.

Hi
Sniff, thank you for the clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

NPM Resource Changed This Pull Request can't be tested by Patchtester

Projects

None yet

Development

Successfully merging this pull request may close these issues.