Skip to content

fix(client): re-export OrderPostStatus from the root entry point - #346

Open
naruto11eth wants to merge 1 commit into
mainfrom
feature/dev-640-export-order-post-status
Open

fix(client): re-export OrderPostStatus from the root entry point#346
naruto11eth wants to merge 1 commit into
mainfrom
feature/dev-640-export-order-post-status

Conversation

@naruto11eth

@naruto11eth naruto11eth commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

AcceptedOrderResponse.status is typed as OrderPostStatus, but the root entry point only re-exported the enum as a type, not as a value. Comparing against a member, response.status === OrderPostStatus.MATCHED, forced consumers to import from @polymarket/bindings/clob, a package documented as not for direct use. Our own integration tests were doing exactly that.

This adds OrderPostStatus to the existing @polymarket/bindings/clob value-export block, alongside OrderResponseErrorCode from the same file, and switches the three integration tests to import it from @polymarket/client.

Changeset: @polymarket/client patch.

Fixes #344

AcceptedOrderResponse.status is typed with it, but only the type was
reachable from @polymarket/client; comparing against a member forced an
import from the internal bindings package. Our own integration tests were
doing exactly that.
@naruto11eth
naruto11eth requested review from cesarenaldi and kartojal and removed request for cesarenaldi September 2, 2026 11:24
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.

[Bug]: OrderPostStatus enum not re-exported from @polymarket/client

2 participants