# Summary

The Date module functionality is gradually being moved into D8 core. Date field was included in 8.0, while more complex functionality is still being worked on (see #2613454: Port Date module functionality missing from 8.x core).

Comments

akalata created an issue. See original summary.

akalata’s picture

akalata CreditAttribution: akalata commented
Related issues: +#2613454: Port Date module functionality missing from 8.x core
akalata’s picture

akalata CreditAttribution: akalata commented
Related issues: +#2543958: [META] DateTime Module Improvements
Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented

Wouldn't it be fairer to mark this Closed (duplicate) to signal that the majority of the functionality actually already lives in core? The 80% use case is covered by core.

akalata’s picture

akalata CreditAttribution: akalata commented
Related issues: +#2161337: Add a Date Range field type with support for end date

I think that "Date is in core" is very misleading - "majority of the functionality" and "80% use case" seems pretty optimistic as well. A single date field, sure, but in the past the Date module provided support for end dates, date repeating... I know date stuff is HARD, but closing this out as "done" when it really isn't feels a little bit like lying to make ourselves look better.

There is a core issue #2161337: Add a Date Range field type with support for end date on adding end date support to core, but that's not until 8.2.x (if that).

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented

I didn't say Closed (won't fix). That would make it look like everything was in core, which I agree would be lying.

I said Closed (duplicate), to indicate that the scope is vastly different: the Date module as it lived in D7 is made obsolete by core, but a subset of it makes sense to live on.

I fully realize not 100% is ported, but we are currently telling the world that the D7 Date module's functionality is simply unavailable in D8. Which is an even bigger lie.

akalata’s picture

akalata CreditAttribution: akalata commented

I see your distinction now, but I'm not sure if Closed (duplicate) = Project has been renamed or made obsolete by another project. really fits here either. Rolling the advanced functionality into core is a goal, but is only one possible solution (the other being 'make it work in contrib').

#2607642: [date] Date - basic field in core was created to indicate basic functionality in core (per #2604604: Decide how to handle projects that are partially (but not completely) in core). Is the problem that the contrib_tracker message at https://www.drupal.org/project/date is referencing this issue and not the 'included in core' one? "A date field is in core" is different from "The Date module that you've known and loved is in core."

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented

Is the problem that the contrib_tracker message at https://www.drupal.org/project/date is referencing this issue and not the 'included in core' one? "A date field is in core" is different from "The Date module that you've known and loved is in core."

Yes, the problem is that message. It's not sufficiently nuanced.

akalata’s picture

akalata CreditAttribution: akalata commented
Issue summary: View changes
Status: Needs work » Closed (duplicate)
Related issues: +#2305073: D8: Date repeat feature requests

Catching up on some of the outstanding issues, looks like the consensus is "work on getting it into core" -- so I concede that Closed (Duplicate) makes the most sense.

afeijo’s picture

afeijo
Primary language Portuguese, Brazil
Location Porto Alegre
CreditAttribution: afeijo as a volunteer commented

I need date repeat feature for my D8 project by next week
I doubt it will be available in time :) So I might need to go creative and build some custom solution here just for my needs
Altought I want to see it in core and I'm willing to help. If you guys can hand me instructions I'd be happy to code along

RKopacz’s picture

RKopacz CreditAttribution: RKopacz commented

I would be happy to help to do some testing if it is needed. I could use the end date, but think that repeating dates should stay in contrib. Also, there was a way to choose the format for both the date and the time on the date picker, but I don't see that anywhere now. If that is not in core, that would be a nice addition to the core datetime feature. For example, I really don't need the seconds field in the timepicker.

MrPaulDriver’s picture

MrPaulDriver CreditAttribution: MrPaulDriver commented

Repeating dates are needed and don't get much of a mention in the porting issue mentioned in the opening post. I see there is some contrib activity but it would be good to get an update about the missing functionality in the date module.

dqd’s picture

dqd
(formerly "diqidoq")
CreditAttribution: dqd as a volunteer and at MAROQQO studios commented

Just for sake of completeness and for those who land here, I post a link to a stackexchange discussion holding links to D8 contrib modules providing features discussed here. NOTE: I am not advocating any of them, since I don't know their feature set nor how they possibly duplicate efforts of core issues: https://drupal.stackexchange.com/questions/193590/how-to-have-recurring-...