feat: introduce wrapperDiv option

[michaelmcandrew]

This PR adds a boolean option wrapperDiv that makes the wrapper div optional in a way that doesn't break the existing API.

I can see the value of the wrapper div in some situations but don't see a reason for it to be required.

And when a wrapperComponent is specified the extra div feels especially unnecessary and gets in the way.

Making it optional allows for cleaner simpler markup and makes, for example, styling easier.

Apologies - I made the PR before discussing but let me know what you think / if it is mergable (or not)

Also, just to say, thanks for a great plugin!!

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[antfu]

What does this mean?

[michaelmcandrew]

I wanted to clarify the relationship between wrapperDiv and wrapperComponent. i.e. explain that if wrapperDiv is set to true and a wrapperComponent is defined, the output will look like this:

<WrapperComponent> <div class='markdown-body'> [markdown here] </div> </WrapperComponent>

We could maybe expand the text in the brackets to 'this will wrap the wrapper div when wrapperDiv=true'

Alternatively, we could remove if it is not worth mentioning (and assume that it is fairly easy to work out what combination of options will generate the desired behaviour).

[antfu]

I see, if you mean on the wrapping order, I think it's fine to keep as-is, as it doesn't make much sense to wrap <div outside of the components anyway.

[michaelmcandrew]

Thanks for merging :)