Bug Fix

Resolve a bug where the "Mark all" button would sometimes throw a JS error

Full Changelog: v1.3.5...v1.3.6

Bug Fixes

Previously, when using complex overlapping ranges, ranges that overlap might not behave as expected. Now, when a field is to be excluded by any criteria it is excluded as expected.

Full Changelog: v1.3.4...v1.3.5

Bug Fix

Previously we didn't save data when only completion status of a day was updated, we now save data on any day change of the calendar to ensure that all updates are captured.

Full Changelog: v1.3.3...v1.3.4

Bug Fix

Due to a bootstrap change in a previous version of RC, "Mark all" buttons would not work as expected when more than 2 were configured. This issue has been resolved.

Bug Fix

Previously, using "mark all" buttons wouldn't correctly re-color indicators. Now indicator colors are correctly updated.

Full Changelog: v1.3.1...v1.3.2

Bug Fix

Previously, if a calendar contained data for a question and, after changes on the record or in config, that question no longer needed to be shown the calendar would throw an error. Now we hide the question as defined by configuration, but keep any data that was entered.

Full Changelog: v1.3.0...v1.3.1

Compression Feature

New compression feature for those storing a lot of data in the calendar.

Full Changelog: v1.2.4...v1.3.0

Allow Negatives

Per user requests both integers and numeric types allow for negative numbers now (i.e. a single "-" at the start of the number).

Full Changelog: v1.2.3...v1.2.4

PHP8 fixes

Previously if viewing the calendar without a start/end date value set a PHP error would be thrown on v8+, that no longer occurs.
Escaping json before passing down to JS.
Renaming license file per Vanderbilt.

Full Changelog: v1.2.2...v1.2.3

Minor PHP8 Fix

Resolving one error that occurs in PHP 8, bump framework version to 14.

Full Changelog: v1.2.1...v1.2.2