<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 8010 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 200, Issue 20<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Updating SCSS lint process to use stylelint (BFL Catalog)<br> 2. Re: Updating SCSS lint process to use stylelint (Renvoize, Martin)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 19 Jul 2022 11:35:36 -0400<br>From: BFL Catalog <catalog@bfli.org><br>To: Paul Derscheid <paul.derscheid@lmscloud.de><br>Cc: Owen Leonard <oleonard@myacpl.org>, Koha Devel<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Updating SCSS lint process to use stylelint<br>Message-ID:<br> <CAMigdofCd+krU-hpehGem=XrqFuxrDqYVxykvNyQVRKS7Z6xDQ@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>What exactly is stylelint? Is this what you get after washing clothes too<br>many times? You know the laundry lint builds up so much it cramps your<br>style!<br><br>Wendy Sharkey<br>Head of Circulation/ Cataloging and IT<br>Bennington Free Library<br>101 Silver Street<br>Bennington, VT 05201<br>(802) 442-9051<br><br><br>On Tue, Jul 19, 2022 at 4:29 AM Paul Derscheid <paul.derscheid@lmscloud.de><br>wrote:<br><br>> Hi Owen,<br>><br>> I recently played around with the SCSS to create a more minimalist version<br>> of the bootstrap OPAC for LMSCloud.<br>> I used the predefined rules and I think they’re reasonable choices<br>> (Although I didn’t cross every rule for sure).<br>><br>> Looking forward to stylint in Koha which I already use for some projects<br>> where I use stylus instead of SCSS. It’s a great tool.<br>><br>> Kind regards<br>><br>> Paul<br>><br>> --<br>> LMSCloud GmbH<br>> Paul Derscheid - Software Engineer<br>> Konrad-Zuse-Platz 8 - D-81829 München<br>> m +49 174 2436308<br>> e paul.derscheid@lmscloud.de<br>> w www.lmscloud.de<br>><br>> > On 18. Jul 2022, at 16:32, Owen Leonard <oleonard@myacpl.org> wrote:<br>> ><br>> > Hi all,<br>> ><br>> > Back when we switched from LESS to SCSS in the OPAC (Bug 20427) I<br>> > added a linting configuration, .scss-lint.yml. I've always configured<br>> > my editor to automatically lint SCSS using this configuration. I don't<br>> > know if anyone else does this too.<br>> ><br>> > In VS Code I was using scss-lint for this, but it's now deprecated.<br>> > They suggest stylelint instead: https://stylelint.io. I'd like to<br>> > propose replacing .scss-lint.yml with .stylelintrc.json, transferring<br>> > most of the same rules.<br>> ><br>> > It could be left up to the individual to install the dependencies, or<br>> > I could update package.json. One nice thing about stylelint is that it<br>> > has a "--fix" feature for some simple rules. This could be build into<br>> > our gulp tasks.<br>> ><br>> > Has anyone else been linting SCSS? If so, does anyone have opinions<br>> > about how our current rule set is working?<br>> ><br>> > -- Owen<br>> ><br>> > --<br>> > Web Developer<br>> > Athens County Public Libraries<br>> > (740) 737-6006<br>> > https://www.myacpl.org<br>> > _______________________________________________<br>> > Koha-devel mailing list<br>> > Koha-devel@lists.koha-community.org<br>> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> > website : https://www.koha-community.org/<br>> > git : https://git.koha-community.org/<br>> > bugs : https://bugs.koha-community.org/<br>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220719/5b4f9de4/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 19 Jul 2022 22:20:38 +0100<br>From: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com><br>To: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Updating SCSS lint process to use stylelint<br>Message-ID:<br> <CAB7SL8Bf3JecoiDQRLEyyKcXOzqjEVC_V-7f3YW3huk9K0KtHg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>I'm in a similar camp to David, though I have touched it a few times here<br>and there.. I wasn't aware of a linter, but would take your lead Owen, I<br>like linters and tidies in general.. having consistent code is clearer code<br>in my book.<br><br>On Tue, 19 Jul 2022, 4:36 pm BFL Catalog, <catalog@bfli.org> wrote:<br><br>> What exactly is stylelint? Is this what you get after washing clothes too<br>> many times? You know the laundry lint builds up so much it cramps your<br>> style!<br>><br>> Wendy Sharkey<br>> Head of Circulation/ Cataloging and IT<br>> Bennington Free Library<br>> 101 Silver Street<br>> Bennington, VT 05201<br>> (802) 442-9051<br>><br>><br>> On Tue, Jul 19, 2022 at 4:29 AM Paul Derscheid <paul.derscheid@lmscloud.de><br>> wrote:<br>><br>>> Hi Owen,<br>>><br>>> I recently played around with the SCSS to create a more minimalist<br>>> version of the bootstrap OPAC for LMSCloud.<br>>> I used the predefined rules and I think they’re reasonable choices<br>>> (Although I didn’t cross every rule for sure).<br>>><br>>> Looking forward to stylint in Koha which I already use for some projects<br>>> where I use stylus instead of SCSS. It’s a great tool.<br>>><br>>> Kind regards<br>>><br>>> Paul<br>>><br>>> --<br>>> LMSCloud GmbH<br>>> Paul Derscheid - Software Engineer<br>>> Konrad-Zuse-Platz 8 - D-81829 München<br>>> m +49 174 2436308<br>>> e paul.derscheid@lmscloud.de<br>>> w www.lmscloud.de<br>>><br>>> > On 18. Jul 2022, at 16:32, Owen Leonard <oleonard@myacpl.org> wrote:<br>>> ><br>>> > Hi all,<br>>> ><br>>> > Back when we switched from LESS to SCSS in the OPAC (Bug 20427) I<br>>> > added a linting configuration, .scss-lint.yml. I've always configured<br>>> > my editor to automatically lint SCSS using this configuration. I don't<br>>> > know if anyone else does this too.<br>>> ><br>>> > In VS Code I was using scss-lint for this, but it's now deprecated.<br>>> > They suggest stylelint instead: https://stylelint.io. I'd like to<br>>> > propose replacing .scss-lint.yml with .stylelintrc.json, transferring<br>>> > most of the same rules.<br>>> ><br>>> > It could be left up to the individual to install the dependencies, or<br>>> > I could update package.json. One nice thing about stylelint is that it<br>>> > has a "--fix" feature for some simple rules. This could be build into<br>>> > our gulp tasks.<br>>> ><br>>> > Has anyone else been linting SCSS? If so, does anyone have opinions<br>>> > about how our current rule set is working?<br>>> ><br>>> > -- Owen<br>>> ><br>>> > --<br>>> > Web Developer<br>>> > Athens County Public Libraries<br>>> > (740) 737-6006<br>>> > https://www.myacpl.org<br>>> > _______________________________________________<br>>> > Koha-devel mailing list<br>>> > Koha-devel@lists.koha-community.org<br>>> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>>> > website : https://www.koha-community.org/<br>>> > git : https://git.koha-community.org/<br>>> > bugs : https://bugs.koha-community.org/<br>>><br>>> _______________________________________________<br>>> Koha-devel mailing list<br>>> Koha-devel@lists.koha-community.org<br>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>>> website : https://www.koha-community.org/<br>>> git : https://git.koha-community.org/<br>>> bugs : https://bugs.koha-community.org/<br>>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220719/70d3728d/attachment-0001.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 200, Issue 20<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>