…responsive design is pretty good for mobile devices. Actually, it depends on your needs.
But what about API, we have an entire track about RESTful APIs, I think it all can be useful for you more or less, it's a complex question, you know…
…bit odd as some assertor() functions doesn't work properly
}
```
I suspect it's the guzzle version issue, it threw 400 error (as it should) before assertions codes were reached so I failed my test.
I am a RESTful newbie, if it's not right…
…1 is not RESTful
OPTION 1:
{
"id": 12,
"programmer": {
"id": 1,
"nickname": "UnitTester",
"avatar": 3
}
}
But, OPTION 2 would be?
OPTION 2:
{
"id": 12,
"programmer": {
"id": 1
}
}
Or maybe OPTION 3?
OPTION 3:
{
"id": 12,
"programmer_id": 1
}
What would the best RESTful way to…
…Seriously :). So, I wouldn't worry about the REST part of it: when you're dealing with sessions and normal "browser web", very little is RESTFUL. For example, imagine 2 users are logged in and both make identical GET requests to /profile. REST says that…
…update, I can't think of much information about this, but yes, you can do this, and I think you could even certainly make a case for it being RESTful. For example, if you're updating a programmer, but also sending data for the programmer…
…there. I tried linda.com but yous were way more helpful. Hope you guys do more videos soon. Would love to see some topics covered e.g., processing third party APIs via crons or writing Restful APIs etc. I've been telling everyone about knpuniversity.
…Why you avoid to use Alice and doctrine:fixtures:load approach in this tutorial, I think it's much more clear?
And second can we use Alice for test RESTfull APIs and is it much proper way then load mock data inside every test method?
…ultimately, this is what it's doing behind the scenes :).
> Yup, I am primarily talking from a standpoint of someone who is building a RESTful API so a 404 page wouldn't work for me
Btw, if the user goes to `/api/songs/foo`…
…Basically the same thing as before, but it looks more RESTful. But let me know what your situation is - I thought you mentioned earlier that API keys would be approved by admins and wouldn't be created in the way that I'm describing above…
…1. Create in the API an endpoint 'https://127.0.0.1:8000/users/me' to retrieve the current user (thanks to the JWT token) and therefore returning a User object with information such as roles ( and others).
The first one isn't technically RESTful…
…operations can't be used with GraphQL (but if you're not using GraphQL, who cares?) and (b) custom operations aren't RESTful... but the rules of REST should never block you from solving your problems :).
Here is an example from the new tutorial - https:…
…this probably makes sense. I would do this with a custom model class and data persister / data provider as you mentioned.
* C) /api/users/{id}/address
This *does* make *some* sense to me - at least from a RESTful standpoint. What I *don't* like is…
…either a 401 if not authenticated or it would return the serialized User information if you *are* authenticated. This isn't a very RESTful endpoint (not the end of the world), so I would probably just build this as a custom route/controller in Symfony…
…shutdown"). That seems a little RPC to me (like your PATCH example).
FOSRestBundle's route generation seems to propose doing a PATCH "/server/myserver/restart" (see: https://github.com/FriendsOfSymfony/FOSRestBundle/blob/master/Resources/doc/5-automatic-route-generation_single-restful-controller.md). This *might…
…seen Fielding argue elsewhere "if it doesn't make sense as a normal RESTful operation, POST as a catch-all is totally fine. Just don't then call it RESTful."
A lot of things make sense as a REST-ish API, not as RESTful API…
…need to be specified in the API : it's REST itself that describe this convention.
My point is that you shouldn't need to do links like these. If the API is RESTful, you can create a flexible client library which use only dynamic pathes…
…do one of the following:
1) The RESTful way: PUT /article/1/published 1 (Write the value true to the article's published sub-resource.) You can also then unpublish with PUT /article/1/published 0
2) The RPC way: POST /articles/publish {aid: 1…
…returning a Battle resource, just with different "depth" of data (that's a different representation). REST would want us to do this in some way that didn't change the URL.
In other words, what is the most RESTful? Well, first, you should choose whether…
Blog
REST Revisited
…and I think it's correct, or close
enough.
One of the seeming advantages of a truly RESTful API is that it has the potential
of being self-describing, which means that you can learn everything you need
to know about the API from the…
x
99