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
{{ message }}
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
We currently sort import statements (with respect to each other), and destructuring bindings inside objects (via the sort-destructure-keys/sort-destructure-keys rule), but we don't sort destructuring withinimport statements; eg:
import {
CREATE_SEGMENTS_EXPERIENCE,
EDIT_SEGMENTS_EXPERIENCE,
DELETE_SEGMENTS_EXPERIENCE,
DEPRIORITIZE_SEGMENTS_EXPERIENCE_PRIORITY,
PRIORITIZE_SEGMENTS_EXPERIENCE_PRIORITY
} from '../actions';
The sort-destructure-keys/sort-destructure-keys plugin only works with objects, but we should be able to do something very similar (and likely simpler because we don't have to worry about nesting) for import statements.
The text was updated successfully, but these errors were encountered:
Requested by Brian here.
We currently sort
import
statements (with respect to each other), and destructuring bindings inside objects (via thesort-destructure-keys/sort-destructure-keys
rule), but we don't sort destructuring withinimport
statements; eg:The
sort-destructure-keys/sort-destructure-keys
plugin only works with objects, but we should be able to do something very similar (and likely simpler because we don't have to worry about nesting) forimport
statements.The text was updated successfully, but these errors were encountered: