Skip to content

Jeview-Display: show an option by its name, not its key - #5

Merged
andududu merged 1 commit into
mainfrom
answer-labels
Sep 21, 2026
Merged

andududu merged 1 commit into
mainfrom
answer-labels

Conversation

@andududu

Copy link
Copy Markdown
Owner

A Jeview-Display request header tells the viewer which part of a choice's criteria to show for each answer (name, or question=field pairs, paths allowed). No header, or no such field on an option: the key is shown, as before. The header never reaches Jev and an unreadable one is ignored rather than refused. Only the hint is stored per call; the viewer learns the names once per question and run from one full call.

Docs: README, llms.txt, the in-app info box. 12 tests pass locally.

🤖 Generated with Claude Code

- The map, the list and the drawer labelled every answer with its option's
  key, because the key is what Jev returns. With coded keys that is a map of
  c0, c1, c2. When the criteria behind the keys are objects, a request can
  now say which part to show: Jeview-Display: name, or a field per question
  (category=name, kind=title); a field may be a path. Like Jeview-Trigger it
  never reaches Jev, and the body is untouched.
- Without the header an option is shown by its key, as before, and so is an
  option that lacks the field. The header is only for show, so one that
  cannot be read is dropped and never refuses a call.
- Only the hint is kept with each call. The viewer reads the names once,
  from one whole call that carries the header, and they then hold for that
  question in that run, earlier calls included. Another run may hang other
  things on the same keys, so it keeps its own names, or its keys.
- In the drawer an option that is a whole object is described by its
  description, not by its JSON.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@andududu
andududu merged commit 495a4e4 into main Sep 21, 2026
2 checks passed
@andududu
andududu deleted the answer-labels branch September 21, 2026 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant