This release focuses on code modernization, improving code quality, and establishing a robust testing framework to ensure stability moving forward. The changes include:
While primarily a bugfix release, this release makes the API functionally complete, so tagging a release candidate. Note that because of a change in what is expected to be passed when retrieving the set of active (now, also sorted) augmenters, it will be necessary to use Smart Date 3.4.1 or newer as of this release, or another formatter with the updated API call.
The main push has been to allow support for recurring dates. Because formatters for recurring dates tend to be more complex, the API was updated to allow a formatter to return a keyed array in its supportsDateAugmenter method, which will cause a separate set of configuration to be available for each array item.
Another quick release, to establish a method for formatters to declare their support for the Date Augmenter API. By implementing a method called supportsDateAugmenter() and having it return TRUE, this module will add the relevant configuration options. Not that the formatter will additionally need to update their viewElements() method.
A quick follow-up release to fix the plugin configuration being saved properly. This being fixed should make the plugins using this API much more useful.
Initial release for the Date Augmenter API module. This module provides a way for plugins to add markup and functionality to a formatter's output, without replacing it wholesale. So instead of having to choose between formatters that offer date range deduplication, add to calendar link, etc. you can use plugins to combine these functions.
