Skip to content

feat!: use semicolons for TypeScript member delimiters - #297

Open
arbrandes wants to merge 1 commit into
openedx:mainfrom
arbrandes:arbrandes/semicolon-member-delimiters
Open

feat!: use semicolons for TypeScript member delimiters#297
arbrandes wants to merge 1 commit into
openedx:mainfrom
arbrandes:arbrandes/semicolon-member-delimiters

Conversation

@arbrandes

Copy link
Copy Markdown
Contributor

Description

Switches the shared ESLint config to require semicolons rather than commas as TypeScript member delimiters, and auto-fixes the repository and test site to match.

This is a breaking change for consumers: the rule is inherited from frontend-base, so lint will fail after upgrading until npm run lint:fix is run.

Closes #296

LLM usage notice

Built with assistance from Claude.

Semicolons are the TypeScript standard, and what the linting configuration
frontend-base replaced enforced. Requiring commas instead forced unrelated
churn into the diff of every repository migrating to frontend-base.

BREAKING CHANGE: Consumers of the shared ESLint config will see member
delimiter errors after upgrading. Run `npm run lint:fix` to resolve them.

Closes openedx#296

Co-Authored-By: Claude <noreply@anthropic.com>
@jesusbalderramawgu

Copy link
Copy Markdown
Contributor

well, following the discussion from here
I think this is the right way to go, we can update later all the frontend apps that need this change, but it is easy.
Thank you, Adolfo!

@diana-villalvazo-wgu

Copy link
Copy Markdown
Contributor

Agree, following the Typescript Standard seems the right pattern to follow 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use semicolons, not commas, for TypeScript member delimiters

4 participants