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

Without param #104

Closed
wants to merge 4 commits into from
Closed

Without param #104

wants to merge 4 commits into from

Conversation

brettz9
Copy link
Collaborator

@brettz9 brettz9 commented Nov 1, 2018

Builds on PR #102

(FWIW, I logged a similar issue at eslint/doctrine#222 but that project is no longer being maintained by ESLint.)

@brettz9 brettz9 mentioned this pull request Nov 1, 2018
…/2.0.0/user-guide/migrating-to-2.0.0#plugins-no-longer-have-default-configurations

- Linting (package.json): Add contributors, homepage, bugs (used on npmjs.com)
- npm: Add `package-lock.json`
…and `allowAugmentsExtendsWithoutParam` and apply to `requireParam` (fixes gajus#100)
…tParam` options to include methods whose class has the tag instead (i.e., @OverRide, @implements, @Augments, or @extends)

- Testing (Update): Deprecated Mocha --compilers flag; see https://github.com/mochajs/mocha/wiki/compilers-deprecation
@gajus
Copy link
Owner

gajus commented Dec 7, 2018

Basically, all the PRs are dirty, because they extend one another and do not provide isolated changes.

@gajus
Copy link
Owner

gajus commented Dec 7, 2018

I think the easiest way to resolve this is to close all the existing PRs are start a new.

@gajus gajus closed this Dec 7, 2018
@gajus gajus mentioned this pull request Dec 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid flagging require-param with @implements present (and possibly also @augments/@extends)
2 participants