Symfony RESTful API: Course 1

Hey Mario,

We do want to release this course, you can see it here: https://knpuniversity.userv... - but unfortunately we do not have any estimations about its release date yet, sorry. Thanks for your patience!

Cheers!

This link shows: "This UserVoice instance does not exist.". I would be very happy if API platform course would be created.

Hey Daniel,

Awesome news for you! We've started working on ApiPlatform course! Well, it's on the planning stage yet, but I think it will be available in a month or two. And yeah, it's a *top* secret! So, shhhhhhh, don't tell anyone ;)

P.S. And the correct link is: https://symfonycasts.uservo...

Cheers!

Wow!

Your voting system is totally awesome.😍 Now I feel that I have influence on topics that you will presents.
I have to tell all my friends 🧑👨👧🎃 to subscribe Symfony Cast and vote like me as soon as possible :D 😇

Thank You!

Hi Victor, I need to start a new project with an API. If I plan to go with API Platform which tutorial should I follow here on SFcast ? Does the Symfony RESTful API: Course will help or it's unrelated ? Thx.

Hey Kaizoku

You can watch our courses about REST API's, it will help you understanding how to develop your own API, how to test it, and some best practices, but we do not talk about "API Platform" on those courses.

Cheers!

Thanks, that's good to know. Will be looking out for it.

Hey Filipe!

You're absolutely right - and we move them into the BaseController eventually (once we actually need them in multiple places - actually it's something we do "offline" between episodes 4 and 5). Of course, many people - like you - will already know this will need to happen, so you can put it directly into BaseController :).

Cheers!

Very cool Hugo do Carmo! Thanks for sharing this - awesome! And yea... hopefully we'll get that PR merged soon - I'm still trying to decide about that last part - if we should add a system to also be able to load .env.ENVIRONMENT files (e.g. .env.test).

Cheers!

Hey joanquilez

Thank you for your honest feedback. We're working on a way to reduce this kind of problems (related to old dependencies) but it will take us some time to deliver it. What I recommend you in the meanwhile is to follow this course on Symfony4. it may cause you some troubles because the architecture changed but it's not that hard, and if you have problems, you can always leave us a message.
Oh, and about the dependencies, I think you will have problems with Guzzle only, but you can install the latest version and adjust the code, the library didn't change too much (at least the functions we use in the tutorial)

Cheers!

Thanks a lot! Following it with Symfony4 is what I'm doing since I wrote the message, but with your answer I am more comfortable with my decision!

Hi there!

You absolutely can just return HTML in your API instead of JSON - it's often an easy shortcut to make updating your HTML page with AJAX really easy. Here's how it would look:

public function someAction()
{
    $html = $this->renderView('mypage/some_template.html.twig', array('twigVar' => 'twigVal'));

    // return pure HTML
    return new Response($html);
    // or return HTML inside JSON, under an "html" key (but this key could be anything).
    return new JsonResponse(array('html' => $html));
}

Cheers!

Hey Henri,

Ah, looks like this issue was already solved - could you follow the http://knpuniversity.com/sc... thread to get it worked? Let me know if it helps.

Cheers!

It's work! Thanks Victor :)

Hey Paweł C.!

You do not need to go through those other REST courses before going through this course :). Those courses give deeper explanations of REST concepts, but I refer to them in this screencast. So, if there is some REST idea that is still not clear in this tutorial, you can quickly look at the other tutorials *if* you want deeper explanation.

I hope that helps! Cheers!

thanks.

Hey David Song!

Sorry for the slow reply - somehow your message landed in SPAM at first >:( - but we rescued it :). In episode 4 of this tutorial, we actually upgraded to Guzzle 6 and made this change. So, I'm happy to say that you can see some working code there: http://knpuniversity.com/sc.... You can get the code by downloading it, or I have a copy of it here: https://gist.github.com/wea...

Let me know if that helps!

Thanks Ryan! withUri() instead of withRequestTarget()!

Hey Bocharsky!

You can start right with this one :). If you're quite new to REST/API stuff and really want to go deep, I'd watch the other one - though in this screencast, we occasionally say "if you want more info, go to this URL to watch part of the REST series" - to help out with this.

Cheers!

There is a lot of information about REST on KnpU. I think I better to start from scratch and I'm almost sure there I discover a useful information for me too. I always open something new for myself with your screencasts. They're a very cognitive and helps to improve the understanding of the subject area! Thanks!

Hey Achilles,

Yes, you could! It's a matter of taste. But both do the same things. Actually, Symfony client is even simpler because it's already pre-installed in Symfony SE, i.e. you don't need to require it manually with Composer. So just use the one you like the most ;)

Cheers!

Thanks :)

Hey Nick!

We haven't started on this yet, but it's up next - so it's still at least several weeks away. YES, it will use FOSRestBundle. I'm not sure about angular yet - but I think it might be a good idea - after all, that's what a lot of people are using to consume those APIs.

Cheers!

Ye Angular would be great! Any news on that front? And also when you are planning to publish the series? Cheers:)

Hey!

On Angular, no plan yet - but I'm going to see if anything angular-specific might be nice to cover as an addendum to this series. I mean, you'll be rocking a very solid API after this series, but if there are any tweaks needed to play even nicer with Angular, maybe we can add something for that after.

The good news is that we're releasing this series right now - expect more next week.

Cheers!

Eagerly awaiting this too, in the meantime, check this out

https://codereviewvideos.co...

Hey Martin,

Actually, it's completely up to you... or probably your API users. Think about your customers, do they want to send another request for fetching addresses or would like to get them in the customer request. My point here is that if API users need all this info at once, I mean fetching a customer info without addresses is pointless for them, so they always will send another request to get missing addresses, then better to include addresses into the /api/customers/123 endpoint response. But if API users need addresses really rare (they are just interested in basic customer info without addresses), then better to make another endpoint like /api/customers/123/addresses to allow fetching this info only when needed. That's it, I really don't see any significant disadvantages in both approaches.

Cheers!

Hey Nick!

Good question! The FosRestBundle is basically a set of various tools - like helping you decode the JSON request, helping serialize the Form errors, doing content-type negotiation and adding a view layer. These are all peripheral tools - and when you get building, you find that you need probably only a few of those. I don't use it in the screencast, though I could have for JSON deserialization and a few other minor things.

Cheers!

Thanks for reply, for a real application though is FosRestBundle and
BazingaHateoasBundle recommended or you think without those you can create a real life professional application without issues and clean enough?

I think FOSRestBundle is a bit like FOSUserBundle - you can use it, or you can fairly easily build that same stuff yourself and get more flexibility. No one option is best - using the bundle gets you setup faster of course :).

BazingaHateoasBundle is *wonderful*, and we will use it later in the series. The question here is, do you really need links in your API? They're all the rage, but it depends on who you're building your API for (e.g. if your API is for your JS frontend, maybe you don't need links, or need very few).

Cheers!

Hey Marcinho,

Good question! Well, it won't be the next tutorial we're released, but we're definitely going to talk about API with Symfony 4.

Cheers!