From 43f28ffd62dec5c4f34c0d589ff654259ca430be Mon Sep 17 00:00:00 2001 From: Lucas Date: Thu, 28 Sep 2023 12:01:53 -0400 Subject: [PATCH] Fix lint --- v4-client-js/examples/cancel_example.ts | 9 ++++++--- v4-client-js/src/clients/composite-client.ts | 2 +- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/v4-client-js/examples/cancel_example.ts b/v4-client-js/examples/cancel_example.ts index 4537821e..64a4cd5c 100644 --- a/v4-client-js/examples/cancel_example.ts +++ b/v4-client-js/examples/cancel_example.ts @@ -24,9 +24,12 @@ async function test(): Promise { /* Note this example places a stateful order. Programmatic traders should generally not use stateful orders for following reasons: - - Stateful orders received out of order by validators will fail sequence number validation and be dropped. - - Stateful orders have worse time priority since they are only matched after they are included on the block. - - Stateful order rate limits are more restrictive than Short-Term orders, specifically max 2 per block / 20 per 100 blocks. + - Stateful orders received out of order by validators will fail sequence number validation + and be dropped. + - Stateful orders have worse time priority since they are only matched after they are included + on the block. + - Stateful order rate limits are more restrictive than Short-Term orders, specifically max 2 per + block / 20 per 100 blocks. - Stateful orders can only be canceled after they’ve been included in a block. */ const longTermOrderClientId = randomInt(MAX_CLIENT_ID); diff --git a/v4-client-js/src/clients/composite-client.ts b/v4-client-js/src/clients/composite-client.ts index ca39e6df..9f74e7fe 100644 --- a/v4-client-js/src/clients/composite-client.ts +++ b/v4-client-js/src/clients/composite-client.ts @@ -520,7 +520,7 @@ export class CompositeClient { const clobPairId = market.clobPairId; if (!verifyOrderFlags(orderFlags)) { - throw new Error('Invalid order flags: ' + orderFlags); + throw new Error(`Invalid order flags: ${orderFlags}`); } let goodTilBlockTime;