-
Notifications
You must be signed in to change notification settings - Fork 194
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
chore(docs): format mdx
files
#754
Conversation
Hey! Thanks for testing it. Could you try |
Right, it indeed breaks the build. But I find a way to both format the mdx file and have a working build. And we have another issue I captured here #756 : the ci should have detected this PR broke the build at first |
065cfa3
to
3c2ccf1
Compare
chore(docs): format
|
Severity Level | Results | |
---|---|---|
Contracts | Critical High Medium Low Note Total |
0 0 0 4 16 20 |
Dependencies | Critical High Medium Low Note Total |
0 0 0 0 0 0 |
For more details view the full report in OpenZeppelin Code Inspector
3c2ccf1
to
1f7842d
Compare
@vplasencia ready for review |
1f7842d
to
c4cb471
Compare
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.
Great work! Thank you very much.
I just left one comment
`prettier` doesn't not have proper support for MDX v3. Docusaurus recommends using `remark` instead. https://docusaurus.io/docs/markdown-features/react re #503
c79f626
to
40f2e15
Compare
Fix #503
prettier
doesn't not have proper support for MDX v3.So we need to use another formatter to format the
mdx
files used for the docs website.Docusaurus recommends
remark
.So this PR sets up remark in the docs apps package and uses it to format all mdx files.
Test plan
yarn format
should be successfulmdx
file:yarn format:write
should reformat it correctlyyarn workspace semaphore-docs start
: should start the server without warnings or errors