Archive this repository
not-an-aardvark opened this issue · 5 comments
agreed! and we might want to deprecated the package via npm deprecate
. https://docs.npmjs.com/cli/deprecate
Using npm deprecate
will cause a warning to be displayed to ESLint users. Since we're not going to be removing valid-jsdoc
and require-jsdoc
for the forseeable future due to our deprecation policy, that seems like it could be annoying since we're presumably not going to be switching to a different JSDoc parser just to support those rules.
Agreed with @not-an-aardvark on this. I think we should wait until these rules are removed (if they ever are - we haven't been removing deprecated rules up to this point).
I've closed all existing PRs and issues. Additionally, I made a quick PR to update the readme so that those coming across the repository can quickly find context around why this project is no longer maintained. I'd like to land that before we archive the repo. Once that lands, I think we're good to go!
That PR has landed, so I'm going to archive this repo.