[Bug]: PostgreSQL `JSONB` column rendering as [object object] on sidebar editor

[YashS96]

Describe the bug

Bug Description

When querying a table with a native PostgreSQL JSONB column, the values are correctly rendered as string strings in the main data grid. However, selecting a row and checking the right-hand "Edit Row" detail panel shows the literal string [object Object] instead of the formatted JSON string or passing it directly to the Monaco editor.

Expected Behavior

The text field inside the right-hand panel should safely stringify the Javascript object payload returned by the Postgres driver via JSON.stringify(value, null, 2) so that it prints as valid readable JSON text.

Proposed Fix

This layout mismatch happens because the frontend input renderer loops over data cells without checking if typeof value === 'object'. Adding a basic type check format helper before rendering values in the sidebar text-area inputs will prevent this default string coercion.

To Reproduce

Steps to Reproduce

1. Connect to any PostgreSQL database instance containing a JSONB type column.
2. Run a query For selecting a Jsonb column.
3. Click on a row to open the right-hand "Edit Row" drawer menu.
4. Observe that the field containing the JSON object parses to [object Object].

OS Version

macOS 26.2 (25C56)

Tabularis Version

v0.13.4

Relevant Log Output

[debba]

Thanks for the report. I tried to reproduce this but the JSONB values render fine on my side, both in the grid and in the Edit Row panel, they come through as formatted JSON text, not [object Object].

You're on v0.13.4; the current release is v0.14.0, so it's worth trying again there first in case it was already fixed in between.

Here's the schema I used to test (no data), in case it helps line up our setups:

CREATE TABLE products (
    id          SERIAL PRIMARY KEY,
    name        TEXT NOT NULL,
    attributes  JSONB,   -- nested object with arrays and sub-objects
    tags        JSONB,   -- array
    price       NUMERIC(10,2),
    meta_json   JSON     -- plain JSON, for comparison with JSONB
);

I covered a few edge cases across rows: a nested object, an array, empty {}/[], all-NULL, and a scalar JSONB (e.g. 42 and "a string").

If you still hit it on v0.14.0, could you share the exact column definition and a sample value that triggers it? A minimal CREATE TABLE + INSERT that reproduces it on your end would let me track it down quickly.