Skip to content

Releases: Liturgical-Calendar/LiturgicalCalendarAPI

Version 3.9

09 Apr 21:01
311ec30
Compare
Choose a tag to compare

New Contributors

Full Changelog: v3.8...v3.9

Version 3.8

01 Feb 00:19
1d4671e
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.7...v3.8

Version 3.7

15 Dec 12:57
52cac97
Compare
Choose a tag to compare
  • fix support for correct ordinal number spelling for any language
  • fix "Year I", "Year II" references which should only concern weekdays of Ordinary Time
  • fix: in cases where the diocesancalendar parameter was set, but the nationalcalendar parameter was not, the national calendar settings were not being picked up correctly
  • fix for Netherlands national calendar data (Ascension on Thursday)

What's Changed

Full Changelog: v3.6...v3.7

Version 3.6

13 Dec 15:34
d635eab
Compare
Choose a tag to compare
  • allow Diocesan calendars to define mobile festivities
  • allow Diocesan calendars to define untilYear properties for festivities that may have changes after a given year
  • remove hardcoding of English and the 5 main European languages and allow for any possible language
  • allow geographic locales, in order to better identify source data for a given national or diocesan calendar
  • remove hardcoding of supported national calendars, and automate the scan for existing calendars

What's Changed

Full Changelog: v3.5...v3.6

Version 3.5

04 Dec 15:41
fe3b965
Compare
Choose a tag to compare
  • Fixes days before / after Epiphany
  • Adds Dutch translation for Netherlands, thanks to Steven van Roode

What's Changed

Full Changelog: v3.4...v3.5

Version 3.4

06 Jun 09:35
d232b2d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.3...v3.4

Version 3.3

27 Jan 14:48
aa0fe57
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.2...v3.3

Version 3.2

23 Jan 12:56
5cf653c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.1...v3.2

Version 3.1

26 Dec 17:59
31735ac
Compare
Choose a tag to compare
  • all calendar data moved from a MySQL database to JSON files, that can be tracked in the repository
  • the Calendar data for the Universal Calendar, as contained in the JSON files, is now translatable to other languages through a Weblate project
  • the frontend and any implementations of the API have been moved to their own separate repositories,
    only the API code remains in this repository
  • the PHP source code for the API has been pretty much completely rewritten, using classes and enum type classes
  • all translatable strings in the PHP source code have been ported to gettext, and are now managed in a Weblate project
  • parameters diocesanpreset and nationalpreset have been renamed to diocesancalendar and nationalcalendar
  • API now supports POST requests that send JSON in the body instead of Form Data
  • Data type can be set through the Accept header rather than the returntype parameter
  • Language can be set through the Accept-Language header rather than the locale parameter
  • Same as tag/release v3.0 with the addition of a single typo fix, an enum that was in camelcase instead of uppercase. This bug was preventing iCal feeds from being generated correctly.

Version 3.0

26 Dec 14:19
3e02918
Compare
Choose a tag to compare
  • all calendar data moved from a MySQL database to JSON files, that can be tracked in the repository
  • the Calendar data for the Universal Calendar, as contained in the JSON files, is now translatable to other languages through a Weblate project
  • the frontend and any implementations of the API have been moved to their own separate repositories,
    only the API code remains in this repository
  • the PHP source code for the API has been pretty much completely rewritten, using classes and enum type classes
  • all translatable strings in the PHP source code have been ported to gettext, and are now managed in a Weblate project
  • parameters diocesanpreset and nationalpreset have been renamed to diocesancalendar and nationalcalendar
  • API now supports POST requests that send JSON in the body instead of Form Data
  • Data type can be set through the Accept header rather than the returntype parameter
  • Language can be set through the Accept-Language header rather than the locale parameter