Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ide/vscode): fix eslint issues on save #23129

Merged
merged 2 commits into from
Jul 4, 2023

Conversation

setchy
Copy link
Collaborator

@setchy setchy commented Jul 4, 2023

Changes

Configures vscode settings to run eslint fixes on save. Helpful for auto-fixing the import order 馃槍

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@setchy setchy requested review from viceice and rarkins July 4, 2023 11:49
@rarkins rarkins changed the title feat(ide/vscode): fix eslint issues on save chore(ide/vscode): fix eslint issues on save Jul 4, 2023
@rarkins rarkins added this pull request to the merge queue Jul 4, 2023
Merged via the queue into renovatebot:main with commit 519fe4c Jul 4, 2023
36 checks passed
@setchy setchy deleted the feature/vscode-eslint-onsave branch July 4, 2023 13:11
@renovate-release
Copy link
Collaborator

馃帀 This PR is included in version 36.0.0 馃帀

The release is available on:

Your semantic-release bot 馃摝馃殌

@renovate-release
Copy link
Collaborator

馃帀 This PR is included in version 35.159.6 馃帀

The release is available on:

Your semantic-release bot 馃摝馃殌

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants