@0xmonaco/react 1.0.53 → 1.0.55

package/dist/hooks/useUserOrders/useUserOrders.js

@@ -857,11 +857,13 @@ export function orderFromEvent(event) {
         // Read from the ACKNOWLEDGEMENT only, and then left alone:
         // `updateOrderFromEvent` spreads the existing order and never rewrites this
         // field, so the value learned here survives every later event. That is
-        // load-bearing rather than incidental — the maker fill does not carry
-        // `postOnly`, and a post-only order rests and therefore fills as a maker,
-        // so re-deriving the field per event would clear it on the one event a
-        // post-only order most often produces and disagree with REST. Only a real
-        // boolean is taken: anything else is not evidence the order was post-only.
+        // load-bearing rather than incidental. Maker fills DO carry `postOnly`
+        // now, but not every frame does: a server predating maker-fill support
+        // omits it there, and the `OrderCancelled` reporting an IOC/market
+        // order's remainder is a payload that declares no `post_only` at all. So
+        // re-deriving the field per event would still clear it against those and
+        // disagree with REST. Only a real boolean is taken: anything else is not
+        // evidence the order was post-only.
         postOnly: typeof data.postOnly === "boolean" ? data.postOnly : undefined,
         // The local revision the merge ranks against. Without it every REST
         // response outranks live state by default and the stream can be undone.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@0xmonaco/react",
-	"version": "1.0.53",
+	"version": "1.0.55",
 	"type": "module",
 	"homepage": "https://docs.0xmonaco.com/sdk/typescript",
 	"main": "./dist/index.js",
@@ -16,8 +16,8 @@
 		"lint": "biome lint ."
 	},
 	"dependencies": {
-		"@0xmonaco/core": "1.0.53",
-		"@0xmonaco/types": "1.0.53"
+		"@0xmonaco/core": "1.0.55",
+		"@0xmonaco/types": "1.0.55"
 	},
 	"devDependencies": {
 		"@types/react": "^19.1.12",