Adding a div compiler

[datapimp]

When developing plugins which modify the ast, I wanted the ability to create simple wrapper divs.

I just noticed the new functionality where you can specify a custom element name and I think this is a good improvement overall. What wasn't clear to me was which element I should use as the base, if what I wanted was just a simple div which wrapped whatever children the node has.

Would be happy to clean up and simplify the implementation or hear about better approaches to solving this.

[wooorm]

Nice approach.
However, instead of making 'div' nodes standard and becoming some sort of HTML syntax tree,
I recommend the following: inside 'visit', there's a test if 'type' exists on 'visitors'. If not, an error is thrown. instead of throwing, maybe test if 'node.data.htmlName' exists, if it does pass it to a function similar to the 'div' one you just created, but maybe call it 'unknown' or something.

In that case, there won't be any issues popping up here for section nodes, main nodes, article nodes...

P.S. Line 632/633 in your pr are superfluous

[datapimp]

What about something like this? In a plugin we have:

exports = function (mdast, options){
  var compiler = mdast.Compiler

  compiler.renderer('section', function(node){

  })

return function(ast){

  }
}

basically some way of accessing the compiler and registering a new renderer function.

[wooorm]

That's in fact possible :) in an 'attacher' there's access to mdast, which has access to the compiler

[wooorm]

I just woke up when I wrote the previous reply. Hope the code in f3b35fe better shows what I meant ;)

[datapimp]

this is great -- thank you