Add support for specifying tag name about metalsmith-prism

[taylorzane]

P.S. Currently I'm getting around this using the syntax:

pre(class='language-coffeescript')
  code(class='language-coffeescript').
    foo = (bar) ->
      # etc...

[robmcguinness]

metalsmith-prism is just a wrapper around Prism.js I believe it only works with the <code> tag.

• PrismJS/prism#867
• PrismJS/prism#869

I'm not sure why the highlighting isn't properly formatted without <pre> tag but when I have a minute I'll take a peek.

[taylorzane]

Well I did a quick hack to lib/index.js and changed it to $(options.tagName || 'code') and I'm able to highlight anything.

I can submit a PR, I just didn't know if the maintainer had a preferred way to do this. I figured I'd open a discussion about it prior to making any modifications.

Example:

[robmcguinness]

Seems simple enough. In the PR:

• include unit test
• update the README options section

I can cut a release today as soon as everything passes.

[robmcguinness]

It looks like Prism automatically adds the appropriate language class prism.js#L731 to the <pre> parent but only when the function fileHighlight() is run on DOMContentLoaded...which is never trigged with this plugin.

Would adding that same behavior into this plugin satisfy your request? I'm trying to stay as close to the Prism.js concepts as much as possible.

Under Basic Usage

Prism does its best to encourage good authoring practices. Therefore, it only works with <code> elements, since marking up code without a <code> element is semantically invalid.