Skip to content

docs(sdk): fix misleading export description in Exports table - #52

Closed
CryptAm wants to merge 1 commit into
ProjectOpenSea:mainfrom
CryptAm:patch-1
Closed

CryptAm wants to merge 1 commit into
ProjectOpenSea:mainfrom
CryptAm:patch-1

Conversation

@CryptAm

@CryptAm CryptAm commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Motivation

The "Exports" table (docs/sdk.md) lists "All types from types/api.ts".

types/api.ts is an internal file path within the repository. Package consumers import types from the root entry point (import type { Collection } from "@opensea/cli"), not from types/api- that subpath does not exist in the package.json exports. The wording is misleading.

Solution

Replaced with "All API response types"- omitting the reference to the internal file to match the style of the other table rows.

The "Exports" table (docs/sdk.md) lists "All types from `types/api.ts`".

`types/api.ts` is an internal file path within the repository. Package consumers import types from the root entry point (`import type { Collection } from "@opensea/cli"`), not from `types/api`- that subpath does not exist in the `package.json` exports. The wording is misleading.

Replaced with "All API response types"- omitting the reference to the internal file to match the style of the other table rows.
@ryanio

ryanio commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator

Thanks @CryptAm. This repo is a read-only mirror of our monorepo, so I recreated your change there in ProjectOpenSea/opensea-devtools#784 (now merged) with you credited as co-author. I adjusted the row slightly to name the import path and an example type: "API response types (e.g. Collection) | TypeScript interfaces for all API responses, imported from @opensea/cli". It will ship in the next cli release. Closing this one since mirror PRs can't be merged directly.

@ryanio ryanio closed this Oct 3, 2026
@CryptAm

CryptAm commented Oct 3, 2026

Copy link
Copy Markdown
Contributor Author

@ryanio
Thank you! May I ask you if I can continue to report bugs to you via PR? I love helping maintain documentation for developers!

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