order_test.cpp and GTC orders

[DanceBot1234]

Just figured out this is only needed with GTC orders!

Not sure if this qualifies as a new issue but I could not get order_test.cpp to work with GTC orders because of rounding issues with tick size.

For example, running order_test.cpp as is results in a 400 error:
Order placement response: 400
Price (0.1700000850000425) breaks minimum tick size rule: 0.01

If anyone is looking for a quick solution, modifying line 368 from
raw_taker = std::floor(raw_taker * 10000) / 10000; // roundDown to 4 decimals

to

raw_taker = std::floor(raw_taker * 100) / 100;        // roundDown to 2 decimals
raw_maker = raw_taker * raw_price;  //  recalc maker amount with new rounded taker amount

works, not sure if that is the proper implementation or not.

[SebastianBoehler]

Thanks for opening a separate issue and for narrowing it down to GTC orders.

I checked this against the official Polymarket Python/TypeScript clients. The original #15 to_wei issue is still fixed, but this was a different bug: the limit/GTC amount builder was not applying the tick-size rounding rules when calculating maker/taker amounts, so the implied price could drift into values like 0.170000085....

The fix is merged in #19 and released as v1.2.4. Limit/GTC and market/FAK paths now use the same tick-size keyed precision config as the official clients. I also added tick_size to the order params so callers can pass cached market metadata instead of forcing an extra order-time API call.

Really appreciate the concrete repro and workaround here. These reports are helpful and make the SDK better.