We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
extending
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the development branch of the Liturgical Calendar API we have implemented a router with various resource paths.
We have also changed the shape of the data that is both ingested and sent in responses, preferring snake_case properties and collections.
We now need to align the extending frontends, and finalize any missing logic in the API while we're at it.
See Liturgical-Calendar/LiturgicalCalendarAPI/issues/220 .
The text was updated successfully, but these errors were encountered:
See Liturgical-Calendar/LiturgicalCalendarAPI/issues/265
Sorry, something went wrong.
JohnRDOrazio
No branches or pull requests
In the development branch of the Liturgical Calendar API we have implemented a router with various resource paths.
We have also changed the shape of the data that is both ingested and sent in responses, preferring snake_case properties and collections.
We now need to align the
extending
frontends, and finalize any missing logic in the API while we're at it.See Liturgical-Calendar/LiturgicalCalendarAPI/issues/220 .
The text was updated successfully, but these errors were encountered: