Problem/Motivation
Bah, we can't update stylelint because of stylelint-formatter-gitlab: https://gitlab.com/leon0399/stylelint-formatter-gitlab/-/issues/3
@longwave in #3439522-16: Update JavaScript dependencies for Drupal 10.3/11.0
Looks like stylelint-formatter-gitlab might be abandoned, at the very least it doesn't work with this change in styleint 16: stylelint-formatter-gitlab.
There seems to be a workaround here: https://gitlab.com/leon0399/stylelint-formatter-gitlab/-/issues/3#note_1..., but that seems to involve running stuff twice, which seems not great.
There's also a non-passing MR here: https://gitlab.com/leon0399/stylelint-formatter-gitlab/-/merge_requests/3
TLDR: We are currently held back in updating stylelint due to lack of nicely formatted gitlab code-quality reports.
I think it's undesirable to be held back in updating dependencies because tooling lags behind.
With not having had any commit since Sep 25, 2022, and no response from a/the maintainer on the MR mentioned above. I think it's safe to say: Not gonna happen, abandoned.
Steps to reproduce
Proposed resolution
https://gitlab.com/gitlab-formatters/stylelint-formatter-gitlab which works with "stylelint": ">=14"
Remaining tasks
Backport this to the gazillion current branches, TBD by the core committers.
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3467309
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3467309-10.5.x-stylelint-formatter-gitlab
changes, plain diff MR !10337
- 3467309-10.4.x-stylelint-formatter-gitlab
changes, plain diff MR !10344
- 11.x
compare
- 3467309-stylelint-formatter-gitlab-prevents-updating
changes, plain diff MR !10129
- 3467309-stylelint-latest
changes, plain diff MR !10131
- 3467309-error-detection
changes, plain diff MR !10132
Comments
Comment #2
spokjeWith the upcoming releases of 10.4.0 and 11.1.0 this issue is as hot as ever.
Comment #3
spokjeComment #4
spokjeComment #5
spokjeComment #11
spokjeComment #12
spokjeMR !10129 shows that when there are no errors, stuff doesn't break.
This run of another issue show that it can actually detect and report issues: https://git.drupalcode.org/issue/drupal-3487817/-/pipelines/340184/codeq...
That report does indeed look like the example report given here: https://gitlab.com/gitlab-formatters/stylelint-formatter-gitlab/-/merge_...
Comment #13
spokjeMirroring status of parent issue, which became critical.
Comment #14
spokjeComment #15
smustgrave commentedSo the output is slightly different now but I think for the better
before
After
But more importantly it found the error I introduced.
Comment #16
spokjeIMHO the output on GitLab is what matters, the grimy internal format to get there is less relevant.
The output on GitLab is advertised in its own repo as looking something like this:
Screenshot from repo
And in our own drupal CSS Linting job: https://git.drupalcode.org/issue/drupal-3487817/-/pipelines/340184/codeq...
Comment #19
longwaveIn the interests of unblocking the Stylelint upgrade let's get this in now. I think the output could be improved - we should fix up the paths so the link in https://git.drupalcode.org/issue/drupal-3487817/-/pipelines/340184/codeq... is clickable - but that can happen in a followup.
Committed and pushed to 11.x and 11.1.x, thanks! Marking PTBP for backport to 10.5.x and 10.4.x.
Comment #23
spokjeFollow-up issue created: #3489795: Correctly link output of files with problems in CSS linting (stylelint) report on GitLab
Comment #24
sourav_paulworking on to port changes into 10.4.x
Comment #25
sourav_paulComment #29
smustgrave commentedRe-rolls seem fine.
Comment #30
longwave@sourav_paul the 10.5.x patch applies fine to 10.4.x, there was no need to open a separate MR.
Committed and pushed 07aa9ecb2f7 to 10.5.x and 4079ec4a177 to 10.4.x. Thanks!