Ah cool, just wondered if it was hardcoded to markdown only or if it supported everything. ^.^
Should note what it supports though, that is also very good SEO stuff. ^.^
How’s it been working for you, any comments, questions, bugs, etc…?
Also, don’t think elixir’s compilers are taken from dependencies, so users might need to add
compilers: Mix.compilers ++ [:protocol_ex], to their
mix.exs file too.
EDIT: Looked over the code a bit, it looks like it’s just being used as a dispatcher, it’s fine for that however it’s more designed for cross-library dispatching rather than just in-library, I’m not sure forcing the users of the library to adjust their compiler field is really needed for in-single-library dispatch, so you could remove ProtocolEx in full and manually dispatch instead. The code will be a touch longer and you’ll need to manually upkeep it, but it’s not a hard task. Though that’s only if you want to get rid of the
:protocol_ex compiler addition for clients and you don’t intend on ever needing cross-library dispatching.
Though it wouldn’t be an issue in any case if Elixir was able to have dependencies add to the compilers list, maybe someday (would help my ASN.1 compiler plugin too)? ^.^;