Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for setting @odata.nextLink on response body #31

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

LCHarold
Copy link

@LCHarold LCHarold commented Apr 9, 2018

This adds support for @odata.nextLink in the response when the result's nextLink property is populated.

This is rather minimally defined at http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.html#_Toc365464689.

The idea here is that we set the nextLink on the response and the caller can use it to get the next page of results when doing pagination.

You can also set the nextLink property on an expanded navigation property's result. If set it will appear in the response body as <navigationPropertyName>@odata.nextLink. This is documented in the spec at http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html#_Expanded_Navigation_Property. In this scenario you've expanded a navigation and need to support pagination through the expanded navigation property.

@alexjpaz
Copy link

alexjpaz commented Apr 4, 2019

Has there been any traction on getting this merged? This would be very beneficial to have in the main project.

@LCHarold
Copy link
Author

LCHarold commented Apr 5, 2019

Has there been any traction on getting this merged? This would be very beneficial to have in the main project.

I just emailed [email protected] to see if he's still maintaining this project (and also odata-v4-parser). Jaystack's homepage calls out this project under "Latest News" so if Viktor doesn't respond I guess Jaystack will be the next place to check with.

@hakimio
Copy link

hakimio commented May 23, 2019

@LCHarold @lazarv
So, is this project dead?

@LCHarold
Copy link
Author

@LCHarold @lazarv
So, is this project dead?

Well, I emailed @lazarv but got no response.

Then I emailed @knightburton - another JayStack employee - and got a response back that he would contact Viktor. So that was encouraging. But still no movement.

@hakimio
Copy link

hakimio commented May 28, 2019

@LCHarold when was that?

@LCHarold
Copy link
Author

LCHarold commented May 28, 2019

@LCHarold when was that?

@knightburton responded back to me on May 22nd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants