Bug: bar links with hash get embraced repeatedly on lint.
See original GitHub issueDescribe the Bug
a bare link with any trailing hash part like https://foo.bar#hash
get embraced with <
and >
repeatedly on lint.
How to Reproduce
Consider https://foo.bar#hash
, when the file is linted three times, would result in <<<https://foo.bar#hash>>>
.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
href: broken links due to URL-encoding hash sign (# => %23)
Hence I am using a hash sign ( # ) in the URL. For example to link the page https://github.com/latex3/hyperref#bug-reports . Here is...
Read more >Hash Tag Links That Don't Headbutt The Browser Window
Using hash-tag links with a fixed position header can be problematic, as the element may be hidden underneath the header as the browser...
Read more >Goto Fail, Heartbleed, and Unit Testing Culture - Martin Fowler
Two computer security flaws were discovered in early 2014: Apple's “goto fail” bug and OpenSSL's “Heartbleed” bug. Both had the potential for widespread...
Read more >3086-macro-metavar-expr - The Rust RFC Book
This RFC proposes a modest but powerful extension to macro syntax that makes it possible to obtain information that the compiler already knows,...
Read more >Keep URL unaffected when anchor link is clicked
window.location.hash = "". is the possible way I could find.
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
I will see about adding this in the change to add formatting YAML arrays. I have been out sick for the past couple of days, so it is taking longer than expected to enact some of these changes, but hopefully I will have this wrapped up today.
This should be fixed on master and in the next release which I plan to put out tonight. Please let us know if it is not fixed on master or in the next release.