Conversation
Web Console deploy preview
|
A row rule counts as a match for every cell of its row, so the first matching rule in the list wins per cell. A row rule listed first paints the whole row; a cell rule listed first keeps its cell and the row rule fills the rest. Schema and prompt describe the same order. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The drawer shell keeps its nodes for a slide-out before unmounting, and both drawers let the shell own visibility. A maximize or restore remounts the cell, so the open state and the unsaved draft (rules, expanded rule, chart config) live in a per-cell session store and come back in place without replaying the entrance. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- Row rule listed after a matching cell rule on the same column now paints the rest of the row - Between bounds accept auto (null): the engine reads the column's current min/max on every result; new between rules default to auto - Text equality ignores case like contains; previous-result rules compare timestamps as instants - Wire default unit is percent like the drawer; wire rejects a flat gradient and a reversed range - Trend store moves into NotebookProvider behind ResultTrendContext, so maximize/restore keeps the baseline - Trend capture has one writer, run from the cells store before render; the grid only reads - Field validation lives once in the engine and serves the drawer and the wire; loaded configs pass a deep structural guard - ResultGridPanel event-bus effect gets deps; the highlight drawer writes its draft from setters; the tool reports its own AI status Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A `newRow` rule paints the whole row of a row whose identity key was not in the previous result. It carries only a color and a display, needs no column, and defaults to a flash. The drawer offers it as "new row" under the previous-result conditions and hides the column and applies-to fields for it. The condition select no longer waits for a column; a missing column is flagged on Save. The agent wire, tool schema, prompt, structural guard, and shared field validation cover the new kind. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A step now carries `from` and a value takes the highest step it reaches; the rule's base color covers values below the lowest step. This matches threshold lists elsewhere. The editor shows the base line first, then each step as ">= N". The wire uses `steps[].from` and `base_color`. The old shape is dropped on load by the structural guard; no migration. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- test each regex match from the start, so g and y no longer skip rows - keep no trend rows for released cells or cells without comparison rules - reject agent rules that the load check would drop on reload - offer highlight rules only when the active result renders a grid Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Highlight rules for notebook result grids
Result grids in notebook cells can now color cells and rows by rule, so a notebook can serve as a live dashboard: watchlists that flash on price moves, threshold breaches that stay colored, heatmap columns, and event tapes that flash new rows.
What you can do
symbolandside. Then use> previous,< previous,changed, orchanged by at leastan absolute or percent amount. Matching cells flash, and> previous/< previousshow a ▲ or ▼ glyph. Timestamps compare as instants.>,≥,<,≤,=,between,is null,contains, andmatchesa regular expression. Text comparisons ignore case. A rule can target one column or all numeric columns.betweenrule with the gradient fill shades every cell of the column from one color at the low bound to another at the high bound, mixed in between and clamped beyond the ends. Leave a bound empty for auto: it follows the column's current minimum or maximum on every refresh, so a heatmap column keeps its full spread as data moves.Agent and MCP
The assistant and the MCP bridge can set or clear a cell's rules with
set_cell_highlight_config, andapply_notebook_statecarrieshighlight_configper cell. Notebook snapshots include the rules.Also in this PR