- Issue created by @VladimirAus
- First commit to issue fork.
- Status changed to Needs work
10 months ago 5:18am 16 June 2024 - Status changed to Needs review
9 months ago 10:28am 15 July 2024 - Status changed to Needs work
9 months ago 2:53pm 15 July 2024 - 🇦🇺Australia VladimirAus Brisbane, Australia
Merge error. Make sure to pull 4.0.x branch
git pull origin 4.0.x
and resolve conflicts.
- Status changed to Needs review
9 months ago 9:29am 16 July 2024 - Status changed to RTBC
8 months ago 12:10pm 29 August 2024 - 🇮🇳India Tirupati_Singh
Hi, as there is no eslint issues and pipeline is Green for eslint hence moving the issue status to RTBC.
- Status changed to Needs work
8 months ago 6:36am 30 August 2024 - 🇦🇺Australia VladimirAus Brisbane, Australia
- New JS functionality are not explained or commented.
- JS: function moved but no comments added.
- eslint is still in red.
- 🇦🇺Australia jannakha Brisbane!
Changes look good.
Tested.
Ready for release.Thanks for your contribution!
-
vladimiraus →
committed 00fee656 on 4.0.x authored by
deepak5423 →
Issue #3452121 by vladimiraus: Gitlab CI: fix stylelint, eslint...
-
vladimiraus →
committed 00fee656 on 4.0.x authored by
deepak5423 →
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
about 1 month ago 10:03am 27 February 2025 - 🇬🇧United Kingdom paulmartin84
This has broken the shorthand module completely and stories can no longer be selected.
if (option.value == 0) {
was changed to:
if (option.value === 0) {
However the zero is actually a string so now it fails to be excluded and then causes the following error
TypeError: Cannot read properties of undefined (reading 'description'), so either need to be changed back or changed to === '0'While this part is being addressed, we shouldn't be excluding zero anyway. Once a story has been selected, there is currently no way to unselect all stories and set it back to 0 The field doesn't have to be set as a a required nor should it have to be be.
The code also has a hardcoded field name in it, which is just not acceptable in a Drupal module. Users should be free to name their fields as they wish.
I'll create a new issue for all of the above, but just putting it here, incase people are wondering why this issue has broken something
- 🇦🇺Australia VladimirAus Brisbane, Australia
Thanks for reporting @paulmartin84.
Committing now.