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

Request for proxy host compatible EntityList paging #69

Open
jcmoore opened this issue Jul 6, 2018 · 0 comments
Open

Request for proxy host compatible EntityList paging #69

jcmoore opened this issue Jul 6, 2018 · 0 comments

Comments

@jcmoore
Copy link

jcmoore commented Jul 6, 2018

EntityList.getNextPage() currently relies on the next_page field in the response's meta. This can lead to complications in environments where the API is being accessed through a proxy -- which may regularly be the case with front-end clients having to deal with CORS constraints.

We're hoping to be able to use t1-node in the Polaris front-end tech stack. Historically (in Compass), paging is handled by manually computing subsequent URLs based on prior result counts and offsets*. Would you consider making an approach like that an option?

(*) I think manual construction of the follow-up URLs is probably more reliable a solution than my current "workaround" which just monkey-patches the host domain:port on the next_page field.

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

No branches or pull requests

1 participant