Media Summary: To begin with, we need an understanding of what our JSON API should do. It doesn't matter whether our JSON API is We've done most of the hard work at this point. We have a working test suite, we can POST in new data, validate it, and save it to ... Towards the end of the previous video we had a working
Create Three Symfony Back Ends Part 1 Project Introduction - Detailed Analysis & Overview
To begin with, we need an understanding of what our JSON API should do. It doesn't matter whether our JSON API is We've done most of the hard work at this point. We have a working test suite, we can POST in new data, validate it, and save it to ... Towards the end of the previous video we had a working We have covered how to GET a single Album by ID. We saw that we would need to have injected the AlbumRepository, and that ... We've defined two Behat features - the healthcheck.feature, and the album.feature. We've seen how the Healthcheck is really all ... This next step is optional, but I like how it cuts down my controller method code even further. We're going to enable and configure ...
Towards the end of the previous video we saw that FOSRESTBundle comes with the concept of a View Layer. By using the View ... The API Platform setup we're using - aka the default provided via docker-compose.yaml - runs a Postgres DB. In the two previous ... We've now got a fresh installation of the API Platform up and running. As already mentioned, the API Platform is very much a full ... We now have our customised Album POST endpoint up and working. In the process we also had to amend the GET endpoint for a ... As our Behat tests rely on being able to "dogfood" our own API in order to run, the most important and immediately urgent task is to ... Our Behat test suite requires that we can POST data into our API in order to setup the Background of any test we run. This is ...
In the previous video we implemented the getAction. As such, we can now GET a single resource -
