chore: use camel case fileds format for response fields (#103)

chore: use camel case fileds format for response fields (#103)

Author: zeljkoX

api-spec/orders-api.yaml

@@ -74,7 +74,7 @@ paths:
                     nullable: true
                     description: Optional message about the submission
                     example: null
-                  order_id:
+                  orderId:
                     type: string
                     description: Unique identifier for the submitted order
                     example: "1fa518079ecf01372290adf75c55858771efcbcee080594cc8bc24e3309a3a09"
@@ -233,13 +233,13 @@ components:
         - Finalized: Order is complete (after claim confirmation)
         - Failed: Order execution failed (with transaction type details)
       enum:
-        - Created
-        - Pending
-        - Executed
-        - Settled
-        - Finalized
-        - Failed
-      example: "Executed"
+        - created
+        - pending
+        - executed
+        - settled
+        - finalized
+        - failed
+      example: "executed"
 
     AssetAmount:
       type: object

crates/solver-discovery/src/implementations/offchain/_7683.rs

@@ -205,6 +205,7 @@ struct IntentRequest {
 /// * `status` - Either "success" or "error"
 /// * `message` - Optional error message when status is "error"
 #[derive(Debug, Serialize)]
+#[serde(rename_all = "camelCase")]
 struct IntentResponse {
 	order_id: String,
 	status: String, // error | success

crates/solver-types/src/order.rs

@@ -157,6 +157,7 @@ pub struct OrderResponse {
 
 /// Status of an order in the solver system.
 #[derive(Debug, Clone, Serialize, Deserialize, PartialEq)]
+#[serde(rename_all = "camelCase")]
 pub enum OrderStatus {
 	/// Order has been created but not yet prepared.
 	Created,