Skip to content

chore: fix formatting generated files with ESLint #47

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
Jan 13, 2023
Merged

Conversation

ota-meshi
Copy link
Member

No description provided.

@@ -112,7 +112,7 @@ function restoreRanges(data: string): number[] {
fix: true,
baseConfig: { rules: { curly: "off" } },
})
const [result] = await engine.lintText(code, { filePath: "ids.ts" })
const [result] = await engine.lintText(code, { filePath: FILE_PATH })
Copy link
Member Author

Choose a reason for hiding this comment

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

It seems that it is no longer formatted if we don't pass the correct file path. I think it's an effect of @typescript-eslint v2 changes.

@MichaelDeBoey MichaelDeBoey changed the title chore: fix script to format generated files chore: fix formatting generated files with ESLint Jan 13, 2023
@MichaelDeBoey MichaelDeBoey merged commit 5e21554 into main Jan 13, 2023
@MichaelDeBoey MichaelDeBoey deleted the fix-script branch January 13, 2023 23:18
@github-actions
Copy link

🎉 This PR is included in version 4.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants