Skip to content

fix(eslint-plugin): make parser services error clearer #132

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

Jump to bottom
Merged
merged 2 commits into from
Jan 23, 2019
Merged

fix(eslint-plugin): make parser services error clearer #132

merged 2 commits into from
Jan 23, 2019

Conversation

JamesHenry
Copy link
Member

fixes #130

@JamesHenry JamesHenry mentioned this pull request Jan 23, 2019
Closed
@JamesHenry
Copy link
Member Author

I have also added the relevant undocumented parser options to the parser README

@JamesHenry JamesHenry merged commit aa9d1e1 into master Jan 23, 2019
@JamesHenry JamesHenry deleted the fix-plugin-error branch January 23, 2019 13:54
armanio123 pushed a commit to armanio123/typescript-eslint that referenced this pull request Jan 24, 2019
@mysticatea @JamesHenry
Fix: prefer-namespace-keyword false positive (fixes typescript-eslint…
1690342 
…#127) (typescript-eslint#132)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
1 more reviewer

@armano2 armano2 armano2 left review comments

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[restrict-plus-operands] Throws "this rule requires you to use @typescript-eslint/parser"
2 participants
@JamesHenry @armano2