Prettier setup

[jiji14]

This PR follows #1068.
To review all the discussions regarding the formatting, please refer to the previous PR.
I created a new PR to maintain a clean and readable branch.

Related Issue

For considerations regarding Prettier, please refer to the following GitHub issue: Prettier Issue #1014.

Configuration Options

Our team has carefully chosen these configuration options, which are based on discussions.
To explore more details, please visit the Prettier documentation on options.

How to Run Prettier

You can format your code using Prettier by running the following command:

npx prettier --write {filename}

Auto-Saving

If you wish to enable auto-saving locally, please follow these steps:

1. Create a .vscode folder at the project's root directory.
2. Inside the .vscode folder, create a settings.json file and include the following code:

{
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true
}

3. Additionally, install the Prettier - Code formatter VSCode extension.

The next PR will set up GitHub Actions for Prettier.

[JGreenlee]

Great work! LGTM

[shankari]

@JGreenlee @jiji14 this is cool, but we need to figure out the timing.

Once I push the onboarding branch to production, I will attempt to merge it into the current master, at which point, we will have hundreds of merge conflicts.

I am tempted to wait until I have merged onboarding, and have you re-run prettier.
Thoughts?

[jiji14]

@JGreenlee @jiji14 this is cool, but we need to figure out the timing.

Once I push the onboarding branch to production, I will attempt to merge it into the current master, at which point, we will have hundreds of merge conflicts.

I am tempted to wait until I have merged onboarding, and have you re-run prettier. Thoughts?

Sounds good to me! Once the merge is completed, I will rerun Prettier and then post the PR again.

[shankari]

@jiji14 merge is now complete! However, the service_rewrite_2023 branch has significantly diverged from master.
So I would suggest the following flow:

• everybody pulls from service_rewrite_2023 to their open/pending branches and resolve conflicts
• you run prettier on service_rewrite_2023
• people again pull from service_rewrite_2023 to their open/pending branches and resolve conflicts

When we next pull from service_rewrite_2023 to master, the prettier changes will come along by default
There will still likely be merge conflicts, but hopefully I can use git merge -X theirs 😄