docs: refresh screenshots for LOOKUP columns (v1.3.0 DoD follow-up)#68
Merged
Conversation
Missed in the original wizard PR: docs/screenshots/*.png and the demo GIF weren't retaken, despite the grid and form UI materially changing (select editors, DISPLAY-labeled options). Regenerates all screenshots via the existing scripts/capture-screenshots.mjs (now with two new blocks for the BROWSE and form LOOKUP dropdowns) and adds them to the README. The demo GIF is untouched — its command sequence never touches a LOOKUP column, so it isn't stale, just silent on the feature; not worth re-recording for this alone.
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.
Summary
Fixes an omission across the v1.3.0 milestone: the Definition of Done requires retaking screenshots when the UI changes, and none of #58–#62's PRs did — despite the grid and form UI materially changing (select editors for lookup columns,
DISPLAY-labeled options, invalid-state outlines on both element types).scripts/capture-screenshots.mjs(following its existing numbered, commented convention) capturing the BROWSE lookup dropdown and the form lookup picker against a real seededSCHEDULES/STAFFexample.LOOKUPcolumns" section to the README screenshot gallery with both new images.docs/screenshots/demo.gifalone — its command sequence (USE,LIST,SEEK,BROWSE) never touches a lookup column, so it isn't stale, just silent on the new feature. Re-recording it wasn't judged worth doing for this alone; happy to if preferred.Test plan
npm test— 446/446 vitest passnpm run build— clean typecheck + build