Prettier config update

[nearestnabors]

In #1752 we discussed what an ideal Prettier config would look like: more space, no trailing commas. Applied everywhere

[react-native-bot]

Deploy preview for react-native ready!

Built with commit bb29bda

https://deploy-preview-1771--react-native.netlify.com

Changes to docs/ are reflected in the next "master" version.

Thank you for your contributions.

_{How to Contribute • Documentation Sources}

[Simek]

This is a Prettier issue, can we ignore this line?

[nearestnabors]

This seems like a pretty big deal. How many other places is it doing something/going to do something similar?

[Simek]

I was bit surprised but it seems that only this line is affected.

I assume that the reason is that in in JS is a keyword and you usually cannot use it as a name for stand-alone variables or functions. Here it's fine because it's static method.

[cHaLkdusT]

Can we also need to update the .prettierrc options for *.js files so that SnackPlayer snippets will also follow the prettier config?

[lcelso]

I loved it.

[Simek]

@cHaLkdusT Prettier rules are extension (not context) based. This means that until JS code is inside md file all *.md rules will apply to this code.

*.js rule only applies to JS files such as website/core/Footer.js.

[elicwhite]

What is the reason for the website code snippets having a different prettier config than the core codebase? I could understand some things like additional spacing making things easier to read, but I’m not sure about the trailing comma change

[nearestnabors]

@TheSavior Trailing commas are unusual in documentation sample code and tutorials—most of our un-Prettier-ed demos don't have them!

I'm not sure why the site and demo JS are handled differently, but I figure it's better not to go changing things in the site code even though the demo code might need to change with convention. So perhaps that's what was intended!

[nearestnabors]

I'm going to close this and retry after the dust of 0.62 settles.