Add initHighlight callable multiple times.

Add a variant of initHighlight function that can be called multiple times. Useful for single-page applications with lazy-loaded content, that don’t wish to specifically target new code blocks and highlight them manually.

Currently this can be accomplished as follows:

hljs.initHighlighting.called = false;
hljs.initHighlighting();

But that seems bad practice as it’s more complicated than necessary, and encourages manipulation of an internal variable.

We could do:

hljs.initHighlighting(true);

But some might not like the boolean trap. In which case, we could do:

hljs.initHighlighting({force: true});

or:

hljs.initHighlighting({once: false});

Thoughts? I can submit a pull request.

[isagalaev]

In the context of single-page applications (SPAs) or AJAX sites, would you not expect the desire to conveniently re-run to be even more common than the run-once behavior?

No, not really. While the desire to highlight new code blocks is pretty straight-forward the details would differ: people use millions of different frameworks with different tools for reacting at new code blocks. Resorting to some global function that does or does not what you want is far less convenient than just calling highlightBlock or highlightAuto on new content. This also takes care of filtering out already highlighted elements.

And if you do want such a function in your particular case it’s a simple two-liner, really:

var blocks = document.querySelectorAll('pre code:not(.hljs)');
Array.prototype.forEach.call(blocks, highlightBlock);

So I’d say highlightBlock is an adequate API and adding wrappers around it is a slippery slope of chasing all the slightly different variants that people would want.

[speige]

+1