Timeline for REST Api - Check if Action is allowed for entity
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2018 at 12:18 | comment | added | Paul | Drop-down was an example, the fact that it's a kendo grid doesn't change my answer. The point is to populate your UI, at some point you're fetching information from the server. When that happens, if you provide metadata about each data elements that includes the URLs to the related API calls possible by the user, you then have that info available to the client for updating the UI appropriately. | |
| Jan 23, 2018 at 12:09 | comment | added | Nico | As I found out now my colleague also can't write comments, so sorry for late answers. He said that the idea is interesting but pretty much not what is possible for us. The picture you see is a Kendo Grid ( table ) and not a dropdown. His question is more over when those kind of informations should be exchanged and how. I will try editing the question in my own wording to get across what he means. | |
| Jan 23, 2018 at 11:47 | history | answered | Paul | CC BY-SA 3.0 |