Fix JSON value viewer crash and add interactive tree view

[the-vampiire]

Summary

• Fix crash when viewing JSON data containing bracket patterns (e.g., [0,23] interpreted as Rich markup tags)
• Add interactive tree viewer for exploring nested JSON structures in Preview (v) and View (V) modes

Problem

JSON data containing bracket patterns like [0,23] was being interpreted as Rich markup tags, causing MarkupError crashes when using Preview (v) or View (V) on cells containing JSON.

Solution

Bug Fix

• Use rich.Syntax for JSON content rendering with proper syntax highlighting
• Set markup=False on Static widgets for non-JSON content to prevent markup parsing
• Store raw value separately for copy functionality

Feature: Interactive JSON Tree Viewer

• New JSONTreeView widget with collapsible tree structure for JSON data
• Tree view is the default for valid JSON, with syntax highlighting as fallback
• Visual indicators: {} for objects (cyan), [] for arrays (magenta) with item counts
• Type-aware value formatting (null, boolean, number, string)

Key Bindings

Key	Action
t	Toggle between tree and syntax view
E / e	Expand all nodes
Z	Collapse all nodes

Files Changed

File	Change
sqlit/shared/ui/widgets_json_tree.py	New JSON tree viewer widget
sqlit/shared/ui/widgets_value_view.py	Add tree/syntax toggle to inline value view
sqlit/domains/results/ui/screens/value_view.py	Add tree/syntax toggle to modal value view

Validation

• ruff check . - passes
• ruff format --check . - passes
• pyright - passes (0 errors)
• pytest tests/ -k sqlite - 31 passed, 6 skipped
• pytest tests/cli/ tests/ui/ - 127 passed, 1 pre-existing failure unrelated to this PR

[the-vampiire]

tree view

syntax view

[Maxteabag]

Nice PR.

But why isn't the keybindings in the footer?

And expanding a node isn't "e", it should have been enter.

It's just textual default.

Expanding a node shouldn't have a keybinding.

Please be careful about integrating your code with the rest of its structure and practices.

[the-vampiire]

yes good points. i will fix these in the morning.

what binding should be used for collapse?

[Maxteabag]

Lower case 'z' is preferred.

[Maxteabag]

When I say integration with rest of the code base I am particularly concerned about duplicated detect json method. Also the code adds manual key handling directly in the widget. Should instead register with ValueViewActiveState._setup_actions to use the hierarchical state machine.

Please use a ValueViewActiveState and create children ValueViewTreeModeState and ValueViewSyntaxModeState.

[the-vampiire]

i did this as a quick fix with claude locally when i encountered the error, but i should have had more respect than to open the PR without reviewing it for idiomatic adherence. thank you for your patience and direction, we have applied all the fixes you suggested.

i am not familiar with TUI development or many of the libs and frameworks in use. but i pushed claude to confirm that all changes aligned with existing patterns (had it find references to compare to).

during final manual testing i introduced a copy submenu for the tree view that makes it easy to copy a value, a field (key:value), or the whole tree. this was modeled after the result view behavior for copy table (tree), row (field) and cell (value).

tree view

added a copy menu (syntax view just copies all):

syntax view

[the-vampiire]

finally, added these tests (from claude):

Test Coverage

Adds regression tests for the JSON tree viewer functionality:

tests/ui/test_json_tree.py - 7 tests for parse_json_value

• Validates the gatekeeper function that determines whether content receives JSON treatment
• Covers valid JSON objects/arrays, Python dict literals, and rejection of plain text/malformed JSON

tests/ui/keybindings/test_state_machine.py - 3 tests for TestValueViewStates

• Validates that toggle_value_view_mode is blocked for non-JSON content
• Validates that collapse_all_json_nodes only works in tree mode
• Follows existing state machine test patterns

Bug caught during testing:

The test_toggle_blocked_for_non_json test identified a missing value_view_is_json check in ValueViewSyntaxModeState.is_active(). Without this fix, the toggle keybinding would have been incorrectly available for non-JSON content.

[the-vampiire]

the only thing i'm unsure about is the uv.lock file. it has a pretty big diff which is unexpected unless recent merges didnt re-install to update it. let me know if you want me to include it or if there are any other changes youd like done.

thanks again for your patience and for the awesome tool. its been a big help for me.