Resource Conflict only works with core Date range fields. Sites using the
date_recur module for recurring events cannot enable conflict
checking on those fields, so overlapping recurrences are saved without any
errors or visibility into conflicts.
Introduce support for Date Recur fields in the conflict manager so time spans
from recurrences can be used for overlap checks. Expose Date Recur fields in
the Resource conflict settings UI and ensure both form validation and presave
checks honour recurring instances when detecting conflicts.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
joelpittetComment #4
joelpittetI think after fighting the CI this is a big enough change. I ensured some of the methods were a bit more fixed in their expected return types and did my best to ensure date_recur is not a incidental dependency.