grav-plugin-api icon indicating copy to clipboard operation
grav-plugin-api copied to clipboard

A REST API plugin for GravCMS

Results 27 grav-plugin-api issues
Sort by recently updated
recently updated
newest added

The plugin is currently not available through the Grav Repository and therefore also not through the GPM. Adding it requires some small extra steps in this repository which can be...

How should the API manage site media? Should there be another endpoint that will allow uploading/deleting images etc? Need to investigate how Grav internally handles media.

feature

We should create a languages translation file for all strings used by the plugin, so that the plugin can be easily translated to other languages in the future, if so...

enhancement

It is possible to define custom fields in a user account in Grav. If you add a custom field to the fields filter list in `api.yaml` config, then you can...

feature

The [test to check whether `updatePlugins` removes null properties](https://github.com/Regaez/grav-plugin-api/blob/master/tests/unit/Handlers/PluginsHandlerTest.php#L160-L185) is buggy: sometimes it passes, sometimes it fails. We should investigate why this test is inconsistent. The functionality appears to work...

bug

There should be some documentation written on the various fields in the plugin's `api.yaml` file, explaining what each one does and how you can configure the plugin. This should be...

documentation

Currently, we only have `Basic` authentication type available to secure the API. There is an [OAuth login plugin](https://github.com/trilbymedia/grav-plugin-login-oauth2) which allows authentication with several different providers. It could be valuable to...

feature

Need to figure out the best way to get/create/modify a modular page. Currently, the `/pages` endpoint only really supports non-modular...

feature

The current config setup doesn't easily allow for configuring nested endpoints. For example, if we have `POST /api/pages/searches`, currently there are only config exposed for the methods for `/api/pages`. But...

enhancement

Perhaps the `setFilter` function could be moved into the abstract `Resource` class and made to be generic, so it's not repeatedly defined in all the different resource types, e.g. ```php...

enhancement