FR: tag not recognised by linter, only tags
See original GitHub issueIs Your Feature Request Related to a Problem? Please Describe.
I’m always frustrated when linter does not delete #
from tags if the YAML metadata key is named as tag
instead of tags
.
Describe the Solution You’d Like
Both tag
and tags
should trigger lint.
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
How to deal with the TSLint error "A project without tags ...
Have you ever faced the following lint error in your Nx monorepo: A project without tags cannot depend on any libraries.
Read more >Not working in html (vue), when </script> tag has another tag in line ...
The linter-js-standard does not work when there is another tag on the same line as the closing </script> tag. It works only if...
Read more >Help:Lint errors/missing-end-tag - MediaWiki
The missing-end-tag error is when a <tag> is opened, but not closed. To fix it, close the opened tag. Example 1: <span> rabbits....
Read more >Do git tags get pushed as well? - Stack Overflow
When I do git tag on the local directory all the tags are present, but when I logon to the remote repository and...
Read more >Frontend: The schema for `.gitlab-ci.yml` is missing support for ...
!reference tag not recognised - BUG. #348276 ... @f_caplette Do you think we can reuse the pipeline editor's text editor for the CI...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting this. It seems this may have been missed for both
aliases
andtags
.The changes are pretty much ready from what I can tell. I will aim for a release tomorrow since that will give me a little more time to make sure there are no issues with it. This change should now be on master and will go out with the next release. Please let us know if there is an issue with it.