Skip to content

feat: abort signal + schema changes#8

Merged
petar-omni merged 1 commit intomainfrom
feat/abort-signal
Jul 14, 2025
Merged

feat: abort signal + schema changes#8
petar-omni merged 1 commit intomainfrom
feat/abort-signal

Conversation

@petar-omni
Copy link
Contributor

No description provided.

@petar-omni petar-omni requested review from Philippoes and Copilot July 14, 2025 13:28
@changeset-bot
Copy link

changeset-bot bot commented Jul 14, 2025

🦋 Changeset detected

Latest commit: 275eac0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@yieldxyz/sdk Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds support for abort signals in the HTTP client and expands the set of recognized networks by introducing "katana" across schemas and mocks.

  • Introduce options?: { signal?: AbortSignal } in customFetch and all generated API methods
  • Add "katana" to all network-related schema constants and update MSW mocks
  • Update changelog to reflect abort signal support and schema changes

Reviewed Changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
src/api/schemas/*Network.ts Added "katana" to each network enum constant
src/api/index.ts Extended API methods to accept an options parameter and pass through to customFetch
src/api/index.msw.ts Updated MSW response mocks to include "katana"
src/api-client.ts Modified customFetch signature to accept abort signals
.changeset/fluffy-ideas-speak.md Added changelog entry for abort signal support
Comments suppressed due to low confidence (2)

src/api/index.ts:32

  • The JSDoc comment for this function should be updated to include the new 'options' parameter and describe its purpose for abort signal support.
export const getYields = (

src/api-client.ts:30

  • Consider adding unit tests to verify that abort signals passed via the 'options' parameter are correctly forwarded to the fetch call and that requests can be aborted as intended.
    signal: options?.signal,

@petar-omni petar-omni merged commit b183928 into main Jul 14, 2025
4 checks passed
@petar-omni petar-omni deleted the feat/abort-signal branch July 14, 2025 13:38
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.

2 participants

Comments