- Issue created by @gorkagr
- First commit to issue fork.
- Status changed to Needs review
12 months ago 12:15pm 19 December 2023 - Status changed to Needs work
12 months ago 12:27pm 19 December 2023 - 🇧🇪Belgium gorkagr
Hi!
You just changed the description but not the actual array value. - 🇧🇪Belgium gorkagr
Hi, sorry for all the comment and edits
I have also noticed the css it is used for rendering the icon
field-icon-date_time
, not evenfield-icon-daterange
, as it takes the category for the rendering due to the new panel. - First commit to issue fork.
- 🇮🇳India sakthi_dev
Hi @gorkagr, updated the code based on comment #6. Should I change the array value or should it stay with 6th comment.
- Status changed to Needs review
12 months ago 1:32pm 19 December 2023 - Status changed to Needs work
12 months ago 7:38pm 19 December 2023 - Status changed to Needs review
12 months ago 9:03pm 19 December 2023 - Status changed to Needs work
12 months ago 1:28am 20 December 2023 - 🇺🇸United States smustgrave
MR should be updated 11.x as the current development branch.
Looking at it though, I think it's the opposite and css should be removed from field_ui to be consistent with how other contrib modules have theirs. But since range is now under date_time the icon doesn't appear regardless so icon should be removed through out.
- Merge request !5914Issue#3409663: Update field type of datetimerange module. → (Closed) created by sakthi_dev
- Status changed to Needs review
12 months ago 2:12pm 21 December 2023 - 🇮🇳India sakthi_dev
Rebased with 11.x and also removed the daterange icon from field_ui and also removed the icon. Please review.
- Status changed to RTBC
12 months ago 5:14pm 21 December 2023 - Status changed to Needs work
12 months ago 11:29pm 21 December 2023 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
We seem to be removing the CSS from both the field ui and the datetime range modules in the latest MR.
That doesn't seem right.
Can we update the issue summary and remove the old approach/EDIT comments so that there's a clear statement of the issue and what the proposed resolution is.
Thanks
- Status changed to Needs review
12 months ago 8:55am 22 December 2023 - Status changed to RTBC
12 months ago 4:25pm 23 December 2023 - 🇺🇸United States smustgrave
Issue summary has been updated. Essentially this is dead code now as datarange isn't it's own category anymore.
-
larowlan →
committed aa55822a on 10.2.x
Issue #3409663 by sakthi_dev, gorkagr, smustgrave: Remove datetime_range...
-
larowlan →
committed aa55822a on 10.2.x
-
larowlan →
committed b90102de on 11.x
Issue #3409663 by sakthi_dev, gorkagr, smustgrave: Remove datetime_range...
-
larowlan →
committed b90102de on 11.x
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Committed to 11.x and backported to 10.2.x to match 📌 Date range should be in the date_time category Needs work
Thanks folks
- Status changed to Fixed
11 months ago 5:37am 28 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.