This should solve the regression/data loss issue introduced by changing to the full icon prefix names.
Closes #3417901
Daniel Moberly (65e140fe) at 13 Sep 15:37
Issue #3386948 by Grimreaper: Fix config schema
Daniel Moberly (a38b5725) at 22 Aug 20:20
Issue #3382648 by Daniel.Moberly: Update to version 6.4.2
Daniel Moberly (8fe2fcd3) at 26 Jul 16:04
Issue #3371188 by sumit-k: Problem installing fontawesome library v...
Daniel Moberly (b8f6b51a) at 25 Jul 16:17
Issue #3376882 by Daniel.Moberly: Brand icons not working
Daniel Moberly (b923d281) at 07 Jul 17:27
Issue #3372915 by Akram Khan: Missing JS once parameter
Daniel Moberly (5b6c538e) at 07 Jul 15:53
Issue #3372324 by hoebekewim: Slow editing pages when using the Ico...
Daniel Moberly (753075a3) at 29 Jun 18:28
Issue #3371082 by breaker_tom, agbockus: Need backwards compatibili...
Daniel Moberly (753075a3) at 29 Jun 18:25
Issue #3371082 by breaker_tom, agbockus: Need backwards compatibili...
This increases PHP requirements to 8
Daniel Moberly (6bc24e95) at 27 Jun 15:54
Issue #3370348 by skyredwang: Compatibility with Core 10.1.*
Daniel Moberly (4a95df61) at 20 Jun 21:18
Issue #3366461 by Grimreaper: Media Library add form support
Daniel Moberly (d341ded1) at 08 Jun 15:41
Issue #3343830 by velo_dev, Shyam_Bhatt: Allow for field descriptio...
Hi,
Yep, I have a global gitignore and more commenting to discuss.
The choice is in the hand of the maintainers.
Hi,
As I am not one of this module maintainers, I was just asking :).
I understood it was to ensure correct version of packages. I recently made contributions into the gin_lb project which as a yarn.lock commited, and even with that I had problems launching scripts...
So definitely a choice for the maintainers depending on their preference.
removed