Skip to content
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

docs(consistent-type-specifier-style): correct default option #220

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/rules/consistent-type-specifier-style.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,10 +37,10 @@ This rule includes a fixer that will automatically convert your specifiers to th

The rule accepts a single string option which may be one of:

- `'prefer-inline'` - enforces that named type-only specifiers are only ever written with an inline marker; and never as part of a top-level, type-only import.
- `'prefer-top-level'` - enforces that named type-only specifiers only ever written as part of a top-level, type-only import; and never with an inline marker.
- `'prefer-inline'` - enforces that named type-only specifiers are only ever written with an inline marker; and never as part of a top-level, type-only import.

By default the rule will use the `prefer-inline` option.
By default the rule will use the `prefer-top-level` option.

## Examples

Expand Down
4 changes: 2 additions & 2 deletions src/rules/consistent-type-specifier-style.ts
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,8 @@ export = createRule<[Options?], MessageId>({
schema: [
{
type: 'string',
enum: ['prefer-inline', 'prefer-top-level'],
default: 'prefer-inline',
enum: ['prefer-top-level', 'prefer-inline'],
default: 'prefer-top-level',
},
],
messages: {
Expand Down
Loading