-
Notifications
You must be signed in to change notification settings - Fork 23
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
Change code-formatter from ESLint to Prettier #1
Conversation
@@ -0,0 +1,3 @@ | |||
node_modules | |||
dist | |||
coverage |
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: New line required
Should we add this as a style rule ?
.nycrc | ||
.nyc_output | ||
coverage/ | ||
coverage/ |
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: Same as previous new line at EOF
]); | ||
}); | ||
|
||
test('product value set and changing it requires confirmation and value changed act', async () => { | ||
const requestHandler = new ControlHandler(new ListControlManager()); | ||
await testE2E(requestHandler, [ | ||
'U: iPhone', TestInput.of(SingleValueControlIntent.of('AppleSuite', { AppleSuite: 'iPhone' })), | ||
'U: iPhone', | ||
TestInput.of(SingleValueControlIntent.of('AppleSuite', { AppleSuite: 'iPhone' })), |
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: Is this ok? Kinda looks weird where we had individual lines alternative for User and Alexa earlier?
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.
Yes there are going to be some cases where the preferred format isn't achieved. I see many reports of people eventually saying they don't mind the change and that the opinionated formatter is liberating. I'm a little skeptical, but I'm willing to try. We might find different ways to address it, and worst case we can use
// prettier-ignore
- ControlManager.handleInternalError can produce a complete response, including setting the shouldEndSession flag. - ControlHandler has three modes for handling exceptions that occur during initialization and/or canHandle. - Default - ControlManager.handleInternalError produces response - Alternative #1 - silently return canHandle=false - Alternative #2 - rethrow exception to topLevel BREAKING CHANGE: - the default behavior for an exception thrown during canHandle is changed. Revert to the old behavior by setting ControlHandler.canHandleThrowBehavior = 'Rethrow'
- ControlManager.handleInternalError can produce a complete response, including setting the shouldEndSession flag. - ControlHandler has three modes for handling exceptions that occur during initialization and/or canHandle. - Default - ControlManager.handleInternalError produces response - Alternative #1 - silently return canHandle=false - Alternative #2 - rethrow exception to topLevel BREAKING CHANGE: - the default behavior for an exception thrown during canHandle is changed. Revert to the old behavior by setting ControlHandler.canHandleThrowBehavior = 'Rethrow'
Description
prettier/@typescript-eslint
to ensure not formatting rules are applied.Motivation and Context
We have been using ESLint as the formatter, however it has some limitations:
Testing
Types of changes
Checklist
License