Skip to content

fix: add ORDER event type to AssetEventType enum#1929

Merged
ryanio merged 1 commit intomainfrom
fix/add-order-event-type
Mar 11, 2026
Merged

fix: add ORDER event type to AssetEventType enum#1929
ryanio merged 1 commit intomainfrom
fix/add-order-event-type

Conversation

@ryanio
Copy link
Collaborator

@ryanio ryanio commented Mar 11, 2026

Summary

  • Add ORDER = "order" to AssetEventType enum to match API response values
  • Add OrderEvent type for order-related activity events
  • Add OrderEvent to the AssetEvent union type

The API returns event_type: "order" for all order-related activities (listings, offers, trait offers, collection offers). This was missing from the SDK, causing consumers to be unable to match on these events.

Note: "order" is a response-only value. The API query filter (event_type param) accepts the specific types: listing, offer, trait_offer, collection_offer.

Based on #1927 by @MuhammadMinhaj — thank you for identifying this gap!

Test plan

  • Verify TypeScript compilation passes
  • Verify existing tests pass
  • Confirm OrderEvent type correctly represents API response shape

🤖 Generated with Claude Code

The API returns event_type "order" for all order-related activities
(listings, offers, trait offers, collection offers). Add the ORDER
enum value and a corresponding OrderEvent response type.

Note: "order" is a response-only value and should not be used as a
query filter in GetEventsArgs.

Co-Authored-By: Muhammad Minhaj <developer.mdminhaj@gmail.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ryanio ryanio merged commit f90500d into main Mar 11, 2026
8 checks passed
@ryanio ryanio deleted the fix/add-order-event-type branch March 11, 2026 19:42
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.

1 participant