-
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
[dev-tool] Fix eslint errors and re-enable linter in dev-tool #18853
Conversation
@@ -20,7 +22,7 @@ export const commandInfo = makeCommandInfo( | |||
); | |||
|
|||
const prettierOptions: prettier.Options = { | |||
...(require("../../../../eslint-plugin-azure-sdk/prettier.json") as prettier.Options), | |||
...(defaultPrettierOptions as prettier.Options), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think this will work. I believe we need the dynamic behavior of require. /cc @witemple-msft
/* eslint-disable @typescript-eslint/no-empty-function */ | ||
error: () => {}, | ||
warn: () => {}, | ||
info: () => {}, | ||
log: () => {} | ||
/* eslint-enable @typescript-eslint/no-empty-function */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT:
/* eslint-disable @typescript-eslint/no-empty-function */ | |
error: () => {}, | |
warn: () => {}, | |
info: () => {}, | |
log: () => {} | |
/* eslint-enable @typescript-eslint/no-empty-function */ | |
error: () => { /** empty body */ }, | |
warn: () => { /** empty body */ }, | |
info: () => { /** empty body */ }, | |
log: () => { /** empty body */ } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good apart from the require change that I believe is worth checking.
FYI There is an overlap between this PR and #18819. /cc @jeremymeng @ramya-rao-a |
Oh gosh, I totally missed that PR, my bad 🤦🏻. Classic. I'll close this one and we can work off the one that's already open. |
Part of work for #17826.