Version Packages - #22
Merged
Merged
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@api-wrappers/api-core@1.1.1
Patch Changes
bedf643: Fix request-lifecycle edge cases and share GraphQL envelope handling:
buildUrlnow inserts query parameters before a URL fragment instead of after it.content-type: application/json, sofetchcan set the correct value (including the multipart boundary).client.graphql()andgraphqlWithResponse(); a non-arrayerrorsfield now throwsApiErrorinstead of silently succeeding, whileerrors: nullis treated as a successful response.graphqlWithResponse()reports GraphQL application errors and malformed envelopes to pluginonErrorhooks via the newBaseHttpClient.notifyError(), matchingclient.graphql().Retry-Afterparsing is centralized so the retry loop and the header rate-limit plugin agree on delay-seconds and HTTP-date formats.timeoutMstakes precedence over the timeout plugin andClientConfig.timeoutMs;createTimeoutPluginrejects non-positive timeouts.onError.ApiError(and subclasses) expose responseheadersand finalurldetails.mergeHeadersskipsnull/undefinedvalues instead of stringifying them.