Repository navigation
docs: fix runnable recipes and tutorial examples #266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dajiaohuang
wants to merge
3
commits into
dai-shi:main
Choose a base branch
from
dajiaohuang:docs/repair-runnable-examples-20261015
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we keep the multiline style?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Restored the original multiline style in both affected Provider examples in a6f388f, keeping the syntax and import fixes unchanged. This follow-up only changes documentation formatting; checked the exact diff and whitespace, without rerunning the earlier React/site tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you check CI error? it's probably complaining because the syntax is correct now.
...might need to be{/* ... */}or something.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked the failing job (run 38861492502, job 117242550207). The failure is not a JSX syntax error:
pnpm testrunstest:format,test:lint,test:typesandtest:spectogether, and it stopped attest:format, which reported a Prettier code-style issue onwebsite/docs/recipes.mdand exited 1. The spec suite never started, so the...lines were not the reported error, and no library code is involved.The format step fails because Prettier reflows the two multiline
Provider/Appexamples back onto a single line, i.e. it would undo the layout you asked to keep in #266 (comment). The minimal fix is to keep the multiline layout and mark those two declarations, so the pushed commit 2b9f2db only adds// prettier-ignoreabove eachconst App = ...in that file — two added comment lines, no other change.Verified locally against this PR head: using the repo's own pinned Prettier 3.4.2 from
pnpm-lock.yamlwith thepackage.jsonprettierconfig,prettier --check website/docs/recipes.mdfails on the previous head (a6f388f) and passes on 2b9f2db. I did not re-run the rest of the suite or trigger a new workflow run, so the other steps are still unverified by me.