Pending #96

Coverage remained the same at 95.018% when pulling c127baa on curbengh:1.3.0 into e463a12 on hexojs:master.

After #92 #93 and #96, will we cover all edge cases that might happened? I am still worrying about the escape options might break on certain edge cases.

• Most of the URLs shouldn't be escaped.
• The html tag inside a html tag shouldn't be escaped.

Anything else?

#96 (comment)

* Most of the URLs shouldn't be escaped.

to clarify (for others reading this), URLs shouldn't be html escaped.

* The html tag inside a html tag shouldn't be escaped.

it depends, it should be escaped when displaying as text (see hexojs/hexo#3704), but shouldn't when used for formatting (bold, italic, etc).

e.g.

<a>How to use the <b> tag?</a>
// should be escaped

<a>This is <b>shocking</b>, wow</a>
// shouldn't be escaped

which is why there is an option to disable escaping.

It is possible to encode url in <style>, #101

#101 merged, I'm merging this.

https://www.npmjs.com/package/hexo-util/v/1.3.0