feat(filter): add after_route_render filter

[jiangtj]

What does it do?

#4048 See discussion here, add after_route_render implement it.

How to test

git clone -b filter https://github.com/jiangtj/hexo.git
cd hexo
npm install
npm test

Screenshots

Pull request tasks

• Add test cases for the changes.
• Passed the CI test.

[coveralls]

Coverage increased (+0.0007%) to 97.424% when pulling 91c70ef on jiangtj:filter into 640b91e on hexojs:master.

[jiangtj]

@SukkaW modified

BTW, Celebrating 1000 test cases. 😂

[curbengh]

Or provide another filter to handle the HTML(after all rendered), after_render:html isn't very accurate, due to md to html or partial will trigger this filter. But expect to filter the final rendered HTML

So this filter only filter the final html file, right? In that case, after_route_render naming can be confusing, as route can refer to any file. I initially thought after_route_render pass every rendered html, js and css to the plugin, but actually only pass the html.

Wouldn't after_html_render (as initially suggested in #4048) be more accurate?

[SukkaW]

Wouldn't after_html_render (as initially suggested in #4048) be more accurate?

@curbengh But it will be confused with after_render:html then.

[curbengh]

it will be confused with after_render:html then

They're functionally similar (to a plugin dev). We can make a note in the docs to recommend after_html_render over after_render:html, if the plugin dev doesn't mind backward compatibility.

[curbengh]

Would it be possible to make after_render:html as an alias of after_html_render? If that's possible, this filter can be made as an internal API (e.g. _after_html_render), and then existing plugins can take advantage of it without changing filter.