Double-quote and semicolon usage not in line with https://docs.cypress.io/

[MikeMcC399]

Situation

Code formatting in this repo is done with a Prettier configuration file. In the case of the following configuration options, these are not defined in .prettierrc so Prettier defaults are used:

Config	default	https://docs.cypress.io/
semi	true	false
singleQuote	false	true

This means that code formatting in this repo is not aligned with the examples on the documentation website https://docs.cypress.io/ or with the default scaffolded Cypress test specs as shown on

End-to-End Testing > Your First Test

---

Instead Cypress test specs, for example cypress/tests/ui/auth.spec.ts, use double-quotes and semicolons:

cypress-realworld-app/cypress/tests/ui/auth.spec.ts

Lines 1 to 18 in d23eba8

	import { User } from "../../../src/models";
	import { isMobile } from "../../support/utils";
	const apiGraphQL = `${Cypress.env("apiUrl")}/graphql`;
	describe("User Sign-up and Login", function () {
	beforeEach(function () {
	cy.task("db:seed");
	cy.intercept("POST", "/users").as("signup");
	cy.intercept("POST", apiGraphQL, (req) => {
	const { body } = req;
	if (body.hasOwnProperty("operationName") && body.operationName === "CreateBankAccount") {
	req.alias = "gqlCreateBankAccountMutation";
	}
	});
	});

Suggestion

Change the Prettier configuration file .prettierrc to

Config	Before (default values)	After
semi	true	false
singleQuote	false	true

to remove the use of semicolons and to use single quotes.

Then re-lint code using:

yarn run prettier

to align with these rules.

[MikeMcC399]

I would like to get feedback from the Cypress.io team before submitting a PR to change all the code formatting. The change is simple to implement, however it impacts all the code, so there will be many files changed. I don't want to do this if there are any concerns from the team.

In a later step I suggest adding @stylistic/eslint-plugin to the repo, which is already in use in other repos like in the cypress-example-kitchensink ESLint config.

If there is a decision to keep the double quotes and semicolons, I suggest adding these explicitly to the Prettier config, so it is clear that it was a conscious decision and not simply left to the default values.