Repository navigation
A list of resources is a view, whatever it joins in - #72
Merged
Merged
Conversation
The view and chart descriptions already said a chart shows values and a view shows resources. A cold agent over MCP, given those descriptions in 2.0.2, still put a household's possessions in a Table chart: it wanted each thing's shop, price and date of purchase beside it, those live on the order and offer, and only a chart shows a join. Nothing said where such values go instead, so the chart looked like the only way, and it showed each thing as its address. ldh-AddResultSetChart now says a query returning a row per resource, with the resource's URI among its variables, belongs in a view however much it joins in; ldh-AddView says the related values are shown by each resource's own page, and what summarises them by a chart beside it. 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
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.
Why
ldh-AddViewandldh-AddResultSetChartalready say a chart shows values and a view shows resources (2.0.2). A cold agent over MCP, running 2.0.2, still put a household's possessions in a Table chart. It wanted each thing's shop, price and date of purchase in the same row; those values live on the order and offer the thing came from, and only a chart shows a join. The descriptions said nothing about where such values go instead, so the chart looked like the only way, and every thing showed up as its address, with no picture or label.What changes
Description text only, no behaviour:
ldh-AddResultSetChart: a query that returns a row per resource, with the resource's URI among its variables, is a list of resources and belongs in a view, however many values from related resources it joins in; a chart of it shows each resource as its address. Chart only what is not one row per resource.ldh-AddView: a list of resources is a view even when what matters about them lives on related resources. Select the resources and let each one's own page show what it links to; put values that summarise the related resources (spend per shop) in a chart beside it.uv run pytest: 1121 passed, 7 skipped.🤖 Generated with Claude Code