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: fix prettier config and run prettier on all files #1460
Conversation
docs/sources/next/examples/get-started-with-k6/reuse-and-re-run-tests.md
Show resolved
Hide resolved
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.
Of course it's hard to vet all the changes but a scan through the PR before the patch was applied to previous versions looked fine to me. We can easily fix forward for some of the odd cases that prettier
has resulted in different HTML output.
Would you like me to check any pages in particular? Perhaps the top 10 k6 pages in https://bi.grafana-ops.net/d/e7be048f-625e-486b-a4d3-37a393fe834f/docs-page-views?orgId=1&var-repository=All&var-path=%5E%2Fdocs%2Fk6?
@jdbaldry I did a quick scan of the main sections and I think everything looks good as well. If people spot anything weird with the formatting, I think we can just fix it going forward. :) |
What?
Fix the prettier configuration file to use the
markdown
parser instead ofbabel
, and run prettier on thedocs/sources
folder. Hopefully this helps with the next PR reviews, as we've been getting small updates that end up with a lot of line changes because of prettier.Checklist
Please fill in this template:
make docs
command locally and verified that the changes look good.docs/sources/next
folder of the documentation.docs/sources/v{most_recent_release}
folder of the documentation.