Skip to content

fix: removing prettier path in vscode config #8255

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 29, 2023

Conversation

Kira-Pilot
Copy link
Member

It looks like we set the prettier path in our VS Code config at some point, probably to get around this bug.
The latest version of VS Code contains a fix for this issue, and so we should take this path out, as it actually now breaks Prettier if you upgrade.

Copy link
Member

@code-asher code-asher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense!

@code-asher
Copy link
Member

code-asher commented Jun 28, 2023

Actually looking at the PR that added it: #8028 (comment)

Maybe there was some issue with the wrong Prettier binary being used? Like if it was globally installed or something? Not sure, we might have to ask @BrunoQuaresma what exactly the problem was.

But we should still merge this anyway since it is broken. Maybe we will want to add the line back later if they fix the issue depending on what @BrunoQuaresma says.

@BrunoQuaresma
Copy link
Collaborator

@Kira-Pilot you are 100% right

@Kira-Pilot Kira-Pilot merged commit 7ca624e into main Jun 29, 2023
@Kira-Pilot Kira-Pilot deleted the fix-prettier/kira-pilot branch June 29, 2023 13:00
@github-actions github-actions bot locked and limited conversation to collaborators Jun 29, 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.

3 participants