-
Notifications
You must be signed in to change notification settings - Fork 7
Add support for custom Parsers of Markdown metadata/attributes (for YAML, Joplin, etc); Make the current Elixir Map parser one of the parser options #30
Comments
I've recently pushed a pr to nimble publisher to have an option for custom parser-do you think this can be done in a way thats compatible between the packages as a hex dependency? |
I liked your idea and the approach to dealing with the parsers. Having it as a hex dependency can be useful for PardallMarkdown, so I don't have to re-invent the wheel. |
The Code.eval_string trick may be good if you keep the data inside your app as nimble publisher does. But when you want to allow parsing external folders possibly modified by others it's a security threat. |
…lement from `PardallMarkdown.MetadataParser`), initially with a parser for elixir maps (the default one) and one for Joplin notes. - The parser can be chosen with the setting `:metadata_parser`. - Removed `:should_try_split_content_title_from_first_line`, since it was specific only to Joplin notes and now the specific parser does not need it. Part of #30 #32
|
Make it similar to dashbitco/nimble_publisher#16 (thank you @dkuku).
Original issue was focused on a single new parser for YAML:
For better compatibility with posts from other static website builders.
The text was updated successfully, but these errors were encountered: