Send Koha-devel mailing list submissions to
koha-devel@lists.koha-community.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
koha-devel-request@lists.koha-community.org
You can reach the person managing the list at
koha-devel-owner@lists.koha-community.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."
Today's Topics:
1. Re: Updating SCSS lint process to use stylelint
(Tomas Cohen Arazi)
2. Re: Updating SCSS lint process to use stylelint (Owen Leonard)
3. Re: Long-term support version of Koha (bug 31008)
(Victor Grousset/tuxayo)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 Jul 2022 08:34:52 -0300
From: Tomas Cohen Arazi <tomascohen@gmail.com>
To: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com>
Cc: Koha Devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Updating SCSS lint process to use stylelint
Message-ID:
<CABZfb=VbfFs3H-dFFpjGK0hETLhYPWiL6mHWFMy9fhh=6fFfpQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Owen!
If the tool is deprecated, let's find another one. I'll follow your lead on
this matter.
El mié, 20 jul 2022 7:34, Renvoize, Martin <martin.renvoize@ptfs-europe.com>
escribió:
> I'm in a similar camp to David, though I have touched it a few times here
> and there.. I wasn't aware of a linter, but would take your lead Owen, I
> like linters and tidies in general.. having consistent code is clearer code
> in my book.
>
> On Tue, 19 Jul 2022, 4:36 pm BFL Catalog, <catalog@bfli.org> wrote:
>
>> What exactly is stylelint? Is this what you get after washing clothes too
>> many times? You know the laundry lint builds up so much it cramps your
>> style!
>>
>> Wendy Sharkey
>> Head of Circulation/ Cataloging and IT
>> Bennington Free Library
>> 101 Silver Street
>> Bennington, VT 05201
>> (802) 442-9051
>>
>>
>> On Tue, Jul 19, 2022 at 4:29 AM Paul Derscheid <
>> paul.derscheid@lmscloud.de> wrote:
>>
>>> Hi Owen,
>>>
>>> I recently played around with the SCSS to create a more minimalist
>>> version of the bootstrap OPAC for LMSCloud.
>>> I used the predefined rules and I think they’re reasonable choices
>>> (Although I didn’t cross every rule for sure).
>>>
>>> Looking forward to stylint in Koha which I already use for some projects
>>> where I use stylus instead of SCSS. It’s a great tool.
>>>
>>> Kind regards
>>>
>>> Paul
>>>
>>> --
>>> LMSCloud GmbH
>>> Paul Derscheid - Software Engineer
>>> Konrad-Zuse-Platz 8 - D-81829 München
>>> m +49 174 2436308
>>> e paul.derscheid@lmscloud.de
>>> w www.lmscloud.de
>>>
>>> > On 18. Jul 2022, at 16:32, Owen Leonard <oleonard@myacpl.org> wrote:
>>> >
>>> > Hi all,
>>> >
>>> > Back when we switched from LESS to SCSS in the OPAC (Bug 20427) I
>>> > added a linting configuration, .scss-lint.yml. I've always configured
>>> > my editor to automatically lint SCSS using this configuration. I don't
>>> > know if anyone else does this too.
>>> >
>>> > In VS Code I was using scss-lint for this, but it's now deprecated.
>>> > They suggest stylelint instead: https://stylelint.io. I'd like to
>>> > propose replacing .scss-lint.yml with .stylelintrc.json, transferring
>>> > most of the same rules.
>>> >
>>> > It could be left up to the individual to install the dependencies, or
>>> > I could update package.json. One nice thing about stylelint is that it
>>> > has a "--fix" feature for some simple rules. This could be build into
>>> > our gulp tasks.
>>> >
>>> > Has anyone else been linting SCSS? If so, does anyone have opinions
>>> > about how our current rule set is working?
>>> >
>>> > -- Owen
>>> >
>>> > --
>>> > Web Developer
>>> > Athens County Public Libraries
>>> > (740) 737-6006
>>> > https://www.myacpl.org
>>> > _______________________________________________
>>> > Koha-devel mailing list
>>> > Koha-devel@lists.koha-community.org
>>> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> > website : https://www.koha-community.org/
>>> > git : https://git.koha-community.org/
>>> > bugs : https://bugs.koha-community.org/
>>>
>>> _______________________________________________
>>> Koha-devel mailing list
>>> Koha-devel@lists.koha-community.org
>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> website : https://www.koha-community.org/
>>> git : https://git.koha-community.org/
>>> bugs : https://bugs.koha-community.org/
>>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : https://www.koha-community.org/
>> git : https://git.koha-community.org/
>> bugs : https://bugs.koha-community.org/
>>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220721/107fcede/attachment-0001.htm>
------------------------------
Message: 2
Date: Thu, 21 Jul 2022 07:53:59 -0400
From: Owen Leonard <oleonard@myacpl.org>
To: Koha Devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Updating SCSS lint process to use stylelint
Message-ID:
<CAO4qe2Nd1xhd4MtxHgBK_vV058VwOukmMmCvkom=HLcT9ek06w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
> I'd like to propose replacing .scss-lint.yml with .stylelintrc.json, transferring
> most of the same rules.
Thanks for the feedback everyone. I'll work on a patch for the lint
config and also one to add stylelint to the CSS build workflow.
-- Owen
------------------------------
Message: 3
Date: Thu, 21 Jul 2022 16:25:19 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: Paul Poulain <paul.poulain@biblibre.com>,
koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Long-term support version of Koha (bug
31008)
Message-ID: <6cb05409-d5e3-a1de-1765-686d04d6a843@tuxayo.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi :)
On 22-06-22 09:47, Paul Poulain wrote:
> Good thing to have a LTS, my main question is about the ecosystem around
> Koha. For example, how to manage Koha LTS regarding
> Debian/Ubuntu/
We already drop and gain support support for Debian/Ubuntu versions
during the lifetime of Koha releases.
> Elastic Search/MariaDB... upgrades ?
Same, we are getting patches for ElasticSearch 7 and OpenSearch support
backported to oldoldstable. And in the past, I recall we dropped ES 5
support to fix a bug with ES 6.
> How can we be sure
> that, in 2 years, Koha LTS will become "unmaintainable" because it
> requires a Perl library that can't be upgraded and the underlying tool
> (OS, search engine...) isn't maintained anymore in the compatible version ?
So it should be ok. Unless there are scenarios not covered by what we
already do?
Cheers,
--
Victor Grousset/tuxayo
------------------------------
Subject: Digest Footer
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
------------------------------
End of Koha-devel Digest, Vol 200, Issue 22
*******************************************