You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every datasource we interact with exposes a REST API. It's fair to expect that developers who know that datasource will be familar with that API.
And almost every adaptor function maps to one or more endpoints in that API.
It would likely be helpful for our docs to expose that mapping. So you want to write job code to to create a new sObject, you'll be expecting to post to salesforce.com/services/data/v60.0/sobjects/whatever. Maybe that URL - or part of it - should be listed in the docs.
Something like this:
We should support an @Map jsdoc tag so that adaptor functions can declare the endpoints they map to.
/**
* @map POST https://{domain}.my.salesforce.com/services/data/v60.0/sobjects/{object}
*/
The text was updated successfully, but these errors were encountered:
Every datasource we interact with exposes a REST API. It's fair to expect that developers who know that datasource will be familar with that API.
And almost every adaptor function maps to one or more endpoints in that API.
It would likely be helpful for our docs to expose that mapping. So you want to write job code to to create a new sObject, you'll be expecting to post to
salesforce.com/services/data/v60.0/sobjects/whatever
. Maybe that URL - or part of it - should be listed in the docs.Something like this:
We should support an @Map jsdoc tag so that adaptor functions can declare the endpoints they map to.
The text was updated successfully, but these errors were encountered: