From 9b25f48a9232aa02e2efffce225de7b8032b5320 Mon Sep 17 00:00:00 2001 From: Tigran Kaginyan Date: Mon, 16 Apr 2018 14:58:03 +0300 Subject: [PATCH] Updated docs based on new import types --- docs/rules/order.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/rules/order.md b/docs/rules/order.md index ca47a5c645..f6ad04c15a 100644 --- a/docs/rules/order.md +++ b/docs/rules/order.md @@ -91,14 +91,13 @@ The enforced order is the same as the order of each element in a group. Omitted 'builtin', // Built-in types are first [{ name: 'private', pattern: '^my-awesome-project/libs' }, 'internal'] // The private types and internal (@myproject) are mixed together { name: 'absolute', pattern: '^src' }, // Then absolute types - ['sibling', 'parent'], // Then sibling and parent types. They can be mingled together - 'index', // Then the index file + ['sibling', 'parent', 'index'], // Then sibling and parent types and index. They can be mingled together // Then the rest: internal and external type ] ``` The default value is `["builtin", "external", "absolute", "parent", "sibling", "index"]`. By default `"absolute"` type will be applied to any import which path starts with `"/"` if you want to change -that behavior you can specify absolute type with ```Object``` literal ```{ name: 'absolute', pattern: // }```. +that behavior you can specify absolute type with ```Object``` literal ```{ name: 'absolute', pattern: // }```. Custom pattern behavior can be applied only for `"absolute"` and `"private"` types You can set the options like this: