use div for surrounding parsed content.

[mightyplow]

see issue #24

[davidowens]

better still would be to make this an option/prop on the <Markdown /> component, the same way as container works

[beausmith]

As #33 allows container tag to be specified as a prop, I suggest closing this PR.

[mightyplow]

Hi, as I understood it, there is now a prop for setting the content wrapper, isn't it? Cheers, mightyplow Beau Smith <[email protected]> schrieb am Di., 7. Aug. 2018, 20:53:

…

@mightyplow <https://github.com/mightyplow> But, if you're going to close this issue… merge #33 <#33> yo! 👯 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABCvza6Arqedyh0MDXGIj2sIk23br0kJks5uOeI7gaJpZM4OOCuW> .

[beausmith]

I replied, thinking the repo owner closed this issue. Then deleted my comment after realizing my mistake. Please add your support to Issue #33 so that we can get that feature merged by @acdlite!

…

On Tue, Aug 7, 2018 at 21:07 mightyplow ***@***.***> wrote: Hi, as I understood it, there is now a prop for setting the content wrapper, isn't it? Cheers, mightyplow Beau Smith ***@***.***> schrieb am Di., 7. Aug. 2018, 20:53: > @mightyplow <https://github.com/mightyplow> But, if you're going to close > this issue… merge #33 > <#33> yo! 👯 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #25 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ABCvza6Arqedyh0MDXGIj2sIk23br0kJks5uOeI7gaJpZM4OOCuW > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABvHEb_25HfBs5BdVa6-0Vjf3Kb6f75ks5uOeWAgaJpZM4OOCuW> .