githubnext/chopinPublic

Let's compose rich plans together

Put the console screenshot beside the task it answers

The picture proving the console is clean has existed since the run that took
it, and nothing in the repository pointed at it. The acceptance asks for it
attached to the PR; there is no PR, because the branch has not been pushed, so
the only mention of `tasks/images/006-console.png` anywhere was the path the
script writes it to. Evidence a reader cannot reach from the work is not
evidence of it.

The task file is where it can live until there is a PR to attach it to. Tasks
003 to 009 already carry their images that way, and the section says what the
check does and what it reports when run against the two keys as they were —
167 duplicate keys, four of eight checks failing — because a check that cannot
fail on the unfixed code proves nothing about the fix.

Retaking it turned up something the picture was saying badly. The caret lands
where the click does, so typing beside the fence had been landing in the
middle of the word that was clicked: the sentence in the photograph read "A
paragraph betTyping beside a fence. ween the blocks." `End` is not the key
that fixes it on macOS — there it scrolls the page and leaves the caret where
it was — so the platform's own end-of-line is asked for instead.
MAMaggie Appleton authored
8b98e41Patch
Parent61b9ccd
3 files changed+24-11 binary
StackedSplit
scripts/check-dev-console.ts+7 −1
tasks/006-fix-duplicate-react-keys.md+17 −0
tasks/images/006-console.png+0 −0

Binary file not shown.