silverstripe-framework/admin
Ingo Schommer 6e0ef669be payloadSchema support in createEndpointFetcher()
Required for REST URLs which require data to be populated on call.
For example, PUT admin/campaigns/set/:id/publish to publish a campaign.
At the time when createEndpointFetcher() is called, the ":id" parameter can not be resolved,
since the "data" argument is passed in once the returned function is evaluated (since the component using it).
Since the whole idea of createEndpointFetcher() is that components shouldn't know about the backend internals,
its not the right place to interpolate urls.

I'm sending through any payload data in addition to replacing URLs, to keep the API simple for the component.
Again, it shouldn't worry about the presence URL interpolation. The trade off here is that data will be submitted
both in the payload (in case of a POST, PUT or DELETE request), as well as (optionally) in the URL.
2016-04-12 22:03:43 +12:00
..
code Remove <IE10 specific workarounds 2016-04-11 14:50:00 +12:00
css Remove <IE10 specific workarounds 2016-04-11 14:50:00 +12:00
font - Add GridfieldActionsComponent 2016-04-06 08:36:37 +12:00
images Updated build artifacts 2016-04-07 23:50:12 +12:00
javascript payloadSchema support in createEndpointFetcher() 2016-04-12 22:03:43 +12:00
scss Remove <IE10 specific workarounds 2016-04-11 14:50:00 +12:00
templates Remove <IE10 specific workarounds 2016-04-11 14:50:00 +12:00
tests Merge remote-tracking branch 'origin/3' 2016-01-20 13:16:27 +13:00
thirdparty Implement client-side routing with Page.js 2016-04-01 13:45:14 +13:00
_config.php API Move ss buttons plugin out of thirdparty 2016-03-21 13:51:33 +13:00
.gitignore MINOR Removing executable flag from all files (thanks miiihi) 2011-09-18 22:04:02 +02:00