- Issue created by @SocialNicheGuru
- π¬π§United Kingdom scott_euser
Not yet but it does not look like it'd be too difficult.
You could add a new chunk of code repeating the date range types like https://git.drupalcode.org/project/unified_date/-/blob/1.x/src/UnifiedDa... but instead the field type being date_recur.
The pattern is field_name:property_name. If property name is blank it searches value property. At a glance here https://git.drupalcode.org/project/date_recur/-/blob/3.5.x/src/Plugin/Fi... looks like you'll need ':start_date' and ':end_date'.
Beyond that assuming the module saves the entity in a normal drupal way when it recurs it should update the unified_date fine.
We should also add tests to the test sub-module (ie, add date_recur to that module info yml, copy in some example field config, add a test).
- πΊπΈUnited States SocialNicheGuru
Attempt at a unifed_date_date_recur submodule
- Status changed to Needs work
about 2 months ago 6:39am 7 November 2024 - π¬π§United Kingdom scott_euser
Thanks for the patch!
Questions (sorry for my lack of understanding of date recur)
- So no modification needed in UnifiedDateManager::getNodeDateFields() to add a new field type?
- The presave is to have the date change when the recurrence of a date happens right?
Next steps I believe would be converting to a merge request and adding test coverage in a test sub-module (I believe it needs to be a test submodule to avoid a dependency (kinda of like how we have view_ajax_history referenced from https://git.drupalcode.org/project/viewsreference for tests only, but not a hard dependency).