api-components-bundle
api-components-bundle copied to clipboard
Creates a flexible API for a website's structure, reusable components and common functionality.
Calling the /me endpoint looks up the current user in the database again. We now use the username to do this instead of the ID. We set the username in...
[Feature] Return location counts for draft resources, and perhaps collections.
If we load `/_routes//contact.json` for example, we are currently trying to look up the path `/contact.json` instead of `/contact` in the json format which is what we want. We should...
Need to add tests for using Amazon S3 with private files to check how it is handled. Perhaps a temporary token is generated which expires shortly afterwards... I hope! If...
Would be nice wouldn't it. We could have our own page with relevant information on how we have handled a request, security, refresh tokens.
Docs need a lot more attention and work. Many features not documented, e.g. groups added to components and many options and guidance on each of the resources/objects. Dynamic pages needs...
- Services should be given names and the classes as aliases. - Deprecations should be addressed - Double check auto-wiring. We should not be auto-wiring in a bundle
Should probably use a sub-request for collections instead of current functionality. E.g. ```php function getCollection() { $subRequest = Request::create($path, $method, [], [], [], [], $body); try { return $this->kernel->handle($subRequest, HttpKernelInterface::SUB_REQUEST);...
I have been battling with my own thoughts on the best way to implement this. Please take a look at how the bundle configuration can currently be used to determine...
Should look into storing doctrine migrations in configured Flysystem storage.