You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diff --git a/src/keyseq.ts b/src/keyseq.ts
index 5caa81a..d5dccbc 100644
--- a/src/keyseq.ts+++ b/src/keyseq.ts@@ -35,12 +35,12 @@ export class MinimalKey {
/** Does this key match a given MinimalKey extending object? */
match(keyevent) {
- // 'in' doesn't include prototypes, so it's safe for this object.- for (let attr in this) {- if (this[attr] !== keyevent[attr]) return false- }- return true- }+ // 'in' doesn't include prototypes, so it's safe for this object.+ for (let attr in this) {+ if (this[attr] !== keyevent[attr]) return false+ }+ return true+ }
}
Prettier handles it correctly.
The text was updated successfully, but these errors were encountered:
My guess is you will be able to reproduce the issue there if you apply the same range to your source that matches your git diff (i.e. what precise-commits is doing for you behind the scenes)
Please could you try and build that reproduction in the playground to confirm?
Yes, I am comparing with running the whole file through prettier.
This issue should maybe be on prettier rather than here. Depends what prettier --range-* is intended to do. Obviously in the precise-commits use this is wrong. Maybe if you just want to format some js in another document --range is fine, though what it's doing here is still pretty weird.
Prettier handles it correctly.
The text was updated successfully, but these errors were encountered: