While on the subject of Markdown content (see #21), we ought to decide and implement, once and for all-until-things-change 😀, the question of which level is responsible for Markdown conversion. Do we define a Prolog::Core::Article as having Markdown body content and a Prolog::Core::User as having Markdown profile content, or do those classes remain as they are now: simple string-attribute containers that attempt no parsing or conversion of their attribute values?
Put it another way: is there any currently envisioned use case, either post-0.5 or otherwise, where those attributes are required to be either simple text or anything other than Markdown or HTML parsed from Markdown?
mitpaladin
commented
8 years ago
While on the subject of Markdown content (see #21), we ought to decide and implement, once and for all-until-things-change 😀, the question of which level is responsible for Markdown conversion. Do we define a
Prolog::Core::Articleas having Markdown body content and aProlog::Core::Useras having Markdown profile content, or do those classes remain as they are now: simple string-attribute containers that attempt no parsing or conversion of their attribute values?Put it another way: is there any currently envisioned use case, either post-0.5 or otherwise, where those attributes are required to be either simple text or anything other than Markdown or HTML parsed from Markdown?