Skip to content

docs(eslint-plugin): [no-type-alias] fix typo #1840

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Apr 3, 2020
Merged

docs(eslint-plugin): [no-type-alias] fix typo #1840

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bc25924
docs(eslint-plugin): fix typo
cherryblossom000 Apr 3, 2020
a9c9fd2
Merge branch 'master' into patch-1
cherryblossom000 Apr 3, 2020
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
2 changes: 1 addition & 1 deletion packages/eslint-plugin/docs/rules/no-type-alias.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ On the other hand, using a type alias as an interface can limit your ability to:
- Debug your code: interfaces create a new name, so is easy to identify the base type of an object
while debugging the application.

Finally, mapping types is an advance technique, leaving it open can quickly become a pain point
Finally, mapping types is an advanced technique and leaving it open can quickly become a pain point
in your application.

## Rule Details
Expand Down