Kasper Østerbye
Kasper Østerbye
I do not see a way in which this can be done. On github it knows in which project we are working, hence `#123` is unique. In pharo it is...
I now see a way in which this can be done. We could support a preprocessor for the source code that allow you accept an extended source, and return pure...
As an alternative design, the substitution could be applied only by the inline parser. The inline parser is the one responsible for bold, links etc as opposed to the block...
Wrt columns, take a look at the `MicTextPresenter class>>exampleCheetSheet`. It is there already.
Yes, that is the meta issues "Several issues is related to handling of children of nodes”. Listed in #323. It is not a hard issue to address implementation wise, but...
I can live with the XML notion of children/elements, and the the attributes as annotations (typically using MicArgumentSplitter). But XML is not in agreement on this - this short discussion...
But yes - I like > * Domain nodes are always in children and can be optional accessible via specific setters and getter. It means that we can access all...
Agreed
I prefer names which indicate what things do rather than what they do (visit). As I have seen composers, writers and a few others I am not sure there is...
Also, there are inline test in the class `MicrodownParserTest` which should be in `MicInlineParserTest`