?
avatar C-Lodder
C-Lodder
6 Jul 2020

Is Joomla no longer linting the SCSS?

I only ask as there are currently 136 issues in Atum's SCSS raised by the linter.

If Joomla doesn't want to lint the SCSS, then the following files can be removed from the repo:

  • Gemfile
  • Gemfile.lock
avatar C-Lodder C-Lodder - open - 6 Jul 2020
avatar joomla-cms-bot joomla-cms-bot - change - 6 Jul 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 6 Jul 2020
avatar brianteeman
brianteeman - comment - 6 Jul 2020

We should be. I spent ages fixing all the errors a few months ago

avatar Hackwar
Hackwar - comment - 21 Jul 2020

will look into this.

avatar Hackwar
Hackwar - comment - 21 Jul 2020

This is a bit strange. As far as I can tell, Hound should be working, at least from a review of our setup. It also threw errors in earlier PRs, specifically those where you, @brianteeman, fixed a bunch of stuff. However in other cases it stayed silent, for example here #28286

I can only guess that Hound was misconfigured at one point. I'm generally not happy with Hound here, because it only checks files that are touched in the current PR and thus somewhere stuff like this slips through. It also uses outdated software.

Long story short: Yes, Joomla still wants and does lint its SCSS. Yes, there are currently issues which we have to solve. The solution to our issues is to switch to a different linter and to move that into Drone.

avatar Hackwar
Hackwar - comment - 29 Jul 2020

This should be fixed by #30196

avatar C-Lodder C-Lodder - change - 29 Jul 2020
Status New Closed
Closed_Date 0000-00-00 00:00:00 2020-07-29 10:51:44
Closed_By C-Lodder
avatar C-Lodder C-Lodder - close - 29 Jul 2020

Add a Comment

Login with GitHub to post a comment