Thomas Threadgold
Thomas Threadgold
Closes #73 - [x] Creates new endpoint to update configs - [x] Updates API specification for new endpoint - [x] Documents new custom event for config update - [x] Updates...
By default, Slim returns HTML pages for various error states. We should override these so that the API will be consistent and always return a JSON structure.
We could leverage the Grav Cache to store the formatted responses of API requests instead of having to fetch and process pages every time. This might result in faster response...
Similar to the advanced access for pages, we could have advanced access for the users resource too. For example, it could be valuable to enable permissions for creating/updating/deleting users based...
The readme file is currently the default template for a Grav plugin. It needs to be updated with more relevant information. - Configuration and setup of plugin - Granting user...
We should add a new configuration option that enables logging for all the API activity. The logs could be stored in `/logs/api.log`. We should first investigate using [the built-in `$grav['log']`...
Add contributing guidelines for plugin development and code of conduct.
Create a `PATCH /configs/{id}` endpoint that allows an authenticated user to change a config settings.
At the moment, only the attributes which are included by default (`api.yaml` specifies limited fields) are shown in the API specification file. The specification should be updated to include _all...
Document development procedures, such as: - commit naming conventions, zappr config - issue/PR process/requirements, and project board - documentation, e.g. specification, postman collection - testing framework/setup - how to debug...