This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
no-redundant-jsdoc: allow @template with comment #3415
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[bugfix] `no-redundant-jsdoc` allow `@template` tag if it has a description Fixes: #3386
adidahiya
approved these changes
Dec 1, 2017
JoshuaKGoldberg
approved these changes
Dec 1, 2017
HyphnKnight
pushed a commit
to HyphnKnight/tslint
that referenced
this pull request
Apr 9, 2018
[bugfix] `no-redundant-jsdoc` allow `@template` tag if it has a description Fixes: palantir#3386
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR checklist
Overview of change:
[bugfix]
no-redundant-jsdocallow@templatetag if it has a descriptionFixes: #3386
/cc @JoshuaKGoldberg @andy-ms
Is there anything you'd like reviewers to focus on?
typescript@2.2 seems to have a parser bug and considers the
*on the next line as comment. Do we want to handle this in the rule? Right now I just added an exception for this version of typescript to the test.CHANGELOG.md entry: