Repository navigation
feat(netlify-api): read response headers such as Link through onResponse - #266
Merged
Merged
Conversation
Netlify pages its lists with page and per_page and links the other pages in a Link header, which a netlify-api caller could not read since a call resolves to the parsed body only. The fetcher now takes the same onResponse call option as vercel-api-js, cloudflare-api-js and keycloak-api, from the Promise client and from Effect calls. Closes #265
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #265
Adds the
onResponsecall option from vercel-api-js, cloudflare-api-js and keycloak-api to the netlify-api fetcher, so a caller can read theLinkheader Netlify pages its lists with. Works fromclient.api,request()and Effect calls.