MHSanaei 1f2769cebf refactor(api): emit JSON-text columns as nested objects ... Inbound, ClientRecord, and InboundClientIps store settings / streamSettings / sniffing / reverse / ips as JSON-text in the DB. The API was passing that text through verbatim, so every consumer had to JSON.parse a string inside a string. Add MarshalJSON / UnmarshalJSON so the wire format is a real nested object, while still accepting the legacy escaped-string shape on write. Frontend dbinbound.js gets a matching coerceInboundJsonField helper for the same dual-shape read path, and inbound.js toJson stops emitting empty/placeholder fields (externalProxy [], sniffing destOverride when disabled, etc.) so the new normalised JSON stays terse. api-docs and the inbound-clone path are updated to the new shape. Controller route lists are regrouped so all GETs sit above POSTs. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-17 19:04:43 +02:00
..
model.go	refactor(api): emit JSON-text columns as nested objects	2026-05-17 19:04:43 +02:00
model_test.go	refactor(api): emit JSON-text columns as nested objects	2026-05-17 19:04:43 +02:00