adds a prettier ignore file

[jpvajda]

This PR adds a .prettierignore file in order to prevent prettier from over writing some formatting choices we've made for our docs.

Relates to

#9777

References

https://prettier.io/docs/en/ignore.html#ignoring-files

[jpvajda]

One thing to note on this before merging ,locally I still saw prettier overwriting the error-handling.mdx file as I was testing the use of * instead of - for markdown bullets, as prettier prefers - and we prefer *. So I was curious if we needed to actually merge this file into the repo before it would actually take effect. I spent about an hour troubleshooting it, and coudln't determine why even with this file, Prettier still made the auto-correction to the file.

A way to test this PR would be to:

0. install the prettier vsCode plugin
1. pull the code down and attempt make a change to the file error-handling.mdx
2. if the ignore file is working, Prettier should completely ignore this file
3. if the ignore file isn't working, Prettier will change all bullets from * to -

[StephenBarlow]

Works for me if it does what it says on the tin!

[jpvajda]

Before I merge, I just wanted to get @benjamn approval on this thanks @StephenBarlow !

[jpvajda]

@alessbell 👋 This is a pretty straight forward PR for using a prettier ignore file in our repo, So I though this may be something you could review.

[alessbell]

@jpvajda yep, this has the intended effect. The only thing I'd note is that we removed Prettier from the repo 2 years ago (#5227), so adding this ignore file only affects those who have a Prettier plugin installed via IDE extension configured to format on save and don't want to have to manually 'save without formatting' (or disable their Prettier plugin).

[jpvajda]

@alessbell 👋

so adding this ignore file only affects those who have a Prettier plugin installed via IDE extension configured to format on save and don't want to have to manually 'save without formatting' (or disable their Prettier plugin).

yes, that would be the intention with this change. 😄 This actually is my exact use case as well. I notice the Circle CI test is now failing so let me do a rebase on this branch and see if that fixes the test failure.

[alessbell]

yes, that would be the intention with this change. 😄 This actually is my exact use case as well

Sounds good to me 👍

I notice the Circle CI test is now failing so let me do a rebase on this branch and see if that fixes the test failure.

FWIW I had a test fail when I opened a PR just now and I just had to click the re-run button via the web UI for them to pass