Skip to content
This repository was archived by the owner on Jan 10, 2024. It is now read-only.

Conversation

@paulroth3d
Copy link
Contributor

Calling forcetkClient.ajax doesn't quite work as ajax adds on 'services/data' to the request, which is already present from successResponse.nextRecordsUrl - and would otherwise result in an invalid url.

This simply removes that section, so a client can call
forcetkClient.queryMore( successResponse.nextRecordsUrl, successHandler, failureHandler )

…andling of the rest pagination urls.

Calling forcetkClient.ajax doesn't quite work as ajax adds on 'services/data' to the request, which is already present from successResponse.nextRecordsUrl.

Signed-off-by: Paul Roth <paulroth3d@gmail.com>
…oolkit.

Signed-off-by: Paul Roth <paulroth3d@gmail.com>
Signed-off-by: Paul Roth <paulroth3d@gmail.com>
Signed-off-by: Paul Roth <paulroth3d@gmail.com>
@metadaddy
Copy link
Contributor

Apologies for the delay - something went wrong with my email notifications from GitHub!

metadaddy pushed a commit that referenced this pull request Nov 9, 2012
Add in queryMore method to the forceTk toolkit
@metadaddy metadaddy merged commit 6514b30 into developerforce:master Nov 9, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants