This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 887
Conflict between object-shorthand-properties-first and object-literal-sort-key #3606
Comments
I was about to make a PR but it seems there is already #2831 that fixes this |
brunolemos
added a commit
to brunolemos/tslint
that referenced
this issue
Dec 23, 2017
Fix palantir#3606 (Conflict between object-shorthand-properties-first and object-literal-sort-key)
brunolemos
added a commit
to brunolemos/tslint
that referenced
this issue
Dec 23, 2017
Fix palantir#3606 (Conflict between object-shorthand-properties-first and object-literal-sort-key)
4 tasks
I created a PR anyway (#3607) because the existing one was outdated and included other features |
brunolemos
added a commit
to brunolemos/tslint
that referenced
this issue
Dec 23, 2017
Fix palantir#3606 (Conflict between object-shorthand-properties-first and object-literal-sort-key)
brunolemos
added a commit
to brunolemos/tslint-config-airbnb
that referenced
this issue
Jan 15, 2018
…-sort-key # `shorthand-first` is available since tslint v5.9.0. See: palantir/tslint#3606 and palantir/tslint#3607
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report
TypeScript code being linted
with
tslint.json
configuration:Actual behavior
The rules conflict. There isn't a single field ordering that matches both rules, resulting on a non-fixable warning.
a, b, c
a, c, b
Expected behavior
Not conflict.
PS: I see this was mentioned on #2040 by @ajafff
Also I noticed
object-shorthand-properties-first
is from another repo but the fix makes more sense to be insideobject-literal-sort-key
The text was updated successfully, but these errors were encountered: