Rename EarmarkParser to Earmark.Parser to avoid conflicts

[josevalim]

Otherwise, if a project depends on both earmark_parser and
earmark at the same time, the module will conflict with each
other.

[josevalim]

Hi @RobertDober, I am aware you are looking for maintainers but if you could include this change and do a new release, it would be very much welcome and appreciated.

Thank you very much for your time! ❤️

[RobertDober]

Now I am confused, I did not do this already?
Well, obviously not, that's why we need a new maintainer, but of course I will do stuff like this as long as I can find some minutes a day ;)

So it is I who thanx you as a matter of fact

[sabiwara]

I couldn't help but notice, shouldn't this be Earmark.ParserProxy (without the double Earmark)? @josevalim
(Sorry if I'm off, I'm not familiar with the project)

[josevalim]

Yeah, good find. I can submit a PR. :) Although perhaps this module can be removed too. :)

[josevalim]

Or perhaps, since it is publicly documented, we should not change its name.

[RobertDober]

I just merged it I did not understand why. I will be little available in the next days, shall I ask Dave to give you or some proxy of you (pun intended) commit rights here and also publish rights to hex.

I will merge and publish as much as I can, but maybe it would be good to have fallback options.

Again thank you for helping out.

[josevalim]

@RobertDober there is no "technical" reason for the change, except that the module was publicly documented before, so it is best to not change its name in a patch version. :)

Regarding the package on Hex, there is no need to worry. If someday you decide to go on a well-deserved holidays/sabbatical/retirement and not touch a computer for several months, Hex has mechanisms in place to inherit a package after some time.

[RobertDober]

Thank you for that explanation.