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
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.
The text was updated successfully, but these errors were encountered:
EntityList.getNextPage()
currently relies on thenext_page
field in the response'smeta
. 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.The text was updated successfully, but these errors were encountered: