quote response exposes both price_impact and priceImpact

[RachitSrivastava12]

summary

the quote response appears to expose inconsistent field names for price impact.

i found both:

• price_impact
• priceImpact

expected

the api should expose one stable field name, or clearly document which one is current and whether the other is deprecated.

actual

clients need to support both names defensively because the response naming is inconsistent.

question

is one of these deprecated?
if so, which field should clients rely on going forward?