Hello Romel,
We have updated the way the kendo datasource works so you now can pass headers directly to the read option instead of settings them on the xhrRequest. However it seems we might have missed to update the documentation.
The updated configuration should be something similar to this:
I apologize for the inconvenience and we will try to update the documentation as soon as possible.
Regards,
Vasil
Telerik
We have updated the way the kendo datasource works so you now can pass headers directly to the read option instead of settings them on the xhrRequest. However it seems we might have missed to update the documentation.
The updated configuration should be something similar to this:
var apiKey = "YOUR-API-KEY"; var typeName = "CONTENT-TYPE-NAME"; var expandExpression = {}; var el = new Everlive(apiKey); var datasource = new kendo.data.DataSource({ type: "everlive", transport: { typeName: typeName, read: { headers: { "X-Everlive-Expand": JSON.stringify(expandExpression) } } }, schema: { model: { id: Everlive.idField, }, } }); datasource.fetch(function() { console.log(datasource.data()); });I apologize for the inconvenience and we will try to update the documentation as soon as possible.
Regards,
Vasil
Telerik
Everlive is now Telerik Backend Services, and is part of the Telerik Platform.