client_metadata no longer able to pass custom value

[sergulec]

Hi, before the most recent update I was passing client_metadata a value . Its now being populated based on order type. Is it possible to inject some values or use another field that will flow into the fill message with custom values (maybe clientId)? My attempt was to change market.Order to take a dictionary for client_metadata but this seems to still get overwritten when fill message comes.
The change was in this commit ee71838
Thanks

[linear]

GH-84 client_metadata no longer able to pass custom value

[samtin0x]

Hi @sergulec, the change was implemented to track usage consistently across both the deprecated and newer Python clients, as well as the JS/TS and Rust clients. Its purpose is to monitor and analyze client behavior, helping understand how the various implementations are being utilized.

Do you have a specific use case so it can be reconsidered adding back custom client_metadata values?

[sergulec]

Hi @sergulec, the change was implemented to track usage consistently across both the deprecated and newer Python clients, as well as the JS/TS and Rust clients. Its purpose is to monitor and analyze client behavior, helping understand how the various implementations are being utilized.

Do you have a specific use case so it can be reconsidered adding back custom client_metadata values?

I was using it to add some data from time of the trade , after some thought its probably not the right place for it as it can be tracked on the client side off the clientId.