Repository navigation
Update the public records conference from the partner's revised questions - #2347
Open
fastfadingviolets wants to merge 2 commits into
Open
fastfadingviolets wants to merge 2 commits into
fastfadingviolets wants to merge 2 commits into
Conversation
…ions The summary now opens with the reworded paragraph and adds a second one on Question 1, with its link written inline because the summary renders as plain text. The first point where the bills match is reworded to ask how requests for the Legislature's records would work. Verified: the YAML loads, its summary and every row match the revised document by text comparison, and prettier passes. Not verified: the page was not rendered, and nothing was synced. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
fastfadingviolets
requested review from
Mephistic,
alexjball,
kiminkim724,
mertbagt,
mvictor55,
nesanders,
sashamaryl and
timblais
as code owners
November 5, 2026 21:31
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The gist rendered as one plain paragraph, which left the public records conference's note on Question 1 as a bare address with no break before it. It is now markdown, read with react-markdown as the ballot question alert is, with links in the page's dotted style opening in a new tab. The feedback line beneath is styled by its place after the gist's text rather than as any second paragraph, so a gist of several paragraphs does not take its look. The public records gist is rewritten as two paragraphs with a real link; the other eight are single plain sentences and read the same. Verified: the conference and ballot question jest suites pass, including a new test that a gist link opens in a new tab; prettier and eslint are clean on the touched files; the real react-markdown renders the public records gist as two paragraphs with a link and the pet equity gist as one. Not verified: the page was not rendered in a browser, so the link style, the paragraph spacing and the feedback line beneath were not looked at, and nothing was synced. The production build was not run. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
Author
had to throw a little ui tweak in there to make the link render nicely; this is what it looks like |
This branch was successfully deployed
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.
The partner revised their questions document for the records access conference, so the public records committee page now reads as they wrote it. The summary opens with the reworded paragraph and adds one on Question 1, which voters approved on Nov. 3 and which takes effect Jan. 1, 2027. The link is written inline because the summary renders as plain text. The first point where the bills match now asks how requests for the Legislature's records would work.
What's in it
🤖 Generated with Claude Code