-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Can't run lint:fix script to resolve lint error #32350
Comments
@jeremymeng is this expected? Previously we could leverage It seems a common issue for RLC clients and you could reproduce it in https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/documentintelligence/ai-document-intelligence-rest. |
Yeah this is likely due to our recent refactoring/improvement around tsconfig files. I am going to try the suggested |
This address the issue when running `lint:fix` using the first suggestion provided by typescript-eslint > 0:0 error Parsing error: ESLint was configured to run on `<tsconfigRootDir>/test/public/utils/recordedClient.ts` using `parserOptions.project`: <tsconfigRootDir>/tsconfig.json That TSConfig uses project "references" and doesn't include `<tsconfigRootDir>/test/public/utils/recordedClient.ts` directly, which is not supported by `parserOptions.project`. Either: >- Switch to `parserOptions.projectService` >- Use an ESLint-specific TSConfig See the typescript-eslint docs for more info: https://typescript-eslint.io/troubleshooting/typed-linting#are-typescript-project-references-supported ------- ### Packages impacted by this PR eslint-plugin ### Issues associated with this PR #32350
@kazrael2119 Is it working now? |
@jeremymeng lint:fix works now, thanks for the fix |
Here is the error message when running
lint:fix
script in latest mainrepro steps:
this issue has happened recently, Three weeks ago, in my refresh pr, I submitted a commit to fix lint error in 634fbea, at that time, lint:fix was useable.
The text was updated successfully, but these errors were encountered: