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

ER: stylelint linter failing after upgrade #5930

Closed
1 of 4 tasks
roslynwythe opened this issue Nov 22, 2023 · 4 comments
Closed
1 of 4 tasks

ER: stylelint linter failing after upgrade #5930

roslynwythe opened this issue Nov 22, 2023 · 4 comments
Assignees
Labels
Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Draft Issue is still in the process of being created ER Emergent Request Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Issue Making: Level 2 Make issue(s) from an ER or Epic milestone: missing role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours time sensitive Needs to be worked on by a particular timeframe

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Nov 22, 2023

Emergent Requirement - Problem

The GitHub Pull Request check "Lint SCSS" is failing.

Issue you discovered this emergent requirement in

Date discovered

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@jaasonw

What happens if this is not addressed

The GitHub Pull Request check "Lint SCSS" will continue to fail. Merging is not blocked but the failure creates confusion and developers don't have the benefit of the SCSS linter output.

Resources

Recommended Action Items

  • Make a new issue
  • Let a Team Lead know

Potential solutions [draft]

As stated by @jaasonw in his comment #5900 (comment), the stylelint configuration file (see resources above) must be updated as described in Stylelint Migration Guide 14.0

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: 0.25pt Can be done in 0.5 to 1.5 hours role missing Complexity: Missing labels Nov 22, 2023

This comment was marked as outdated.

@roslynwythe roslynwythe added Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Issue Making: Level 2 Make issue(s) from an ER or Epic role: back end/devOps Tasks for back-end developers Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly size: 1pt Can be done in 4-6 hours and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. Complexity: Missing size: 0.25pt Can be done in 0.5 to 1.5 hours role missing labels Nov 22, 2023
@roslynwythe roslynwythe self-assigned this Nov 22, 2023
@roslynwythe roslynwythe added the Draft Issue is still in the process of being created label Nov 22, 2023

This comment was marked as resolved.

@t-will-gillis
Copy link
Member

Hi Roslyn-

FYI I had created a previous ER #5048 a few months ago for this issue. I did a lot of exploration with this and I had found the folllowing (see the previous ER also):

  • as you note, the failure is occurring because the Superlinter is not recognizing the scss anymore with Stylelint 14, which is the main customSyntax error (line 79) that keeps popping up.
Current linter error Screenshot 2023-11-24 201139
  • yes to adding the line regarding "extends": ["stylelint-config-standard-scss"] (I had used "stylelint-config-recommended-scss", but same result)
  • After adding the lines above, I had run into a heap of issues. I found adding the "extends" line took care of the customSyntax error, i.e. that the Superlinter was recognizing the scss again, however in place of the one error there were 22 new syntax errors. (Here is a workflow run) Errors that seem to be cropping up because our code is using old syntax like "map-get()" (line 77) whereas the updated syntax is "map.get()".
After adding "extends" line Screenshot 2023-11-24 201045
  • Some of these new syntax errors can be automatically addressed by using the Sass Migrator, which refactors the Sass to match the latest syntax,
  • However once the Sass Migrator is run, I found that there are still errors, and that Docker either will not load the website at all, or the website runs on Docker with no styling at all.

I realize this is not very helpful...

@roslynwythe
Copy link
Member Author

Closing as not planned because it was a duplicate; I discovered an existing ER #5048 for the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Draft Issue is still in the process of being created ER Emergent Request Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Issue Making: Level 2 Make issue(s) from an ER or Epic milestone: missing role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Development

No branches or pull requests

4 participants