-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fixtures Guide #1160
Fixtures Guide #1160
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
If y'all have a ton of revisions for the guide, let me know and we can move it back to Notion! Due to the code moving about it was easier for me to work directly in Markdown, but I can gladly move back there for revisions |
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.
Please make all the example code ts
. I added some suggestions but it's probably better to do it in one commit.
Co-authored-by: Tim Nolet <[email protected]>
Co-authored-by: Tim Nolet <[email protected]>
@tnolet Tags are updated! Also I finally found the gosh-darned linter setting that was automatically setting my code blocks to be |
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.
LGTM
Affected Components
Pre-Requisites
npm run lint
)