Date Range Field

Fixed

• Fixed type error when using field through GraphQL

Added

• Craft 4 🚀

Added

• Craft CMS 4 compatibility

Added

• Added `isNotPast` option (#31)

Fixed

• Use field handle instead of name in EntryQueryBehavior (#26)

Fixed

• Plugin now works with columnSuffix introduces in Craft CMS 3.7.0 (#26)

Added

• PostgreSQL support

Added

• Elements can now be sorted by date rang fields

Added

• Add a field option and validtor to force the end date later than start date (#23)

Fixed

• Fixed an issue with `formatted()` when the field didn't use time fields (#22)

Fixed

• Fixed an issue with `formatted()` where the start date was used instead of the end date.

Added

• `formatted()` now outputs dates in the current site locale

Added

• Added more options to the `formatted()` option and documentation on how to use them (#15)

Fixed

• Fixed an issue where the field wasn't working from the quick post widget (#14)

Added

• When the field is added to element overview, the values are now formatted based on the current user's locale (#10)

Added

• Full support for Craft's GraphQL API. (#8)

  Fixed

• isFuture on the field value is now based on the start date instead of the end date.

Fixed

• Field labels are now translatable
• When saving a field with only a start date, we'll now use that as value for the end date as well. #4

Added

• Added french translation of the field labels (Thanks @ockam, #6)
• Added dutch translations of the field labels
• Added optional includeToday parameter to entry query behaviour

Added

• `isFuture() and getIsFuture()` now use the end date to determine when an event is over

Added

• `isPast(), isOnGoing() and isFuture()` can now be used in entry queries, passing along the field handle you want to be used to the function. (requires MySQL 5.7 or higher)

Added

• The field can now be displayed on element overview pages in the CP
• Added the getFormatted option to the field to display all data in 1 line

Fixed

• Fixed an issue where using isOngoing() wouldn't use the correct data and woul