Markdown support - how best to do that?

[starbelly]

@gorenje

then there is the Earmark parser that seems to produce an AST tree but not html or am I wrong there?

This is actually much simpler than others have alluded to. I’ll see if I can make a thing happen in the next week or so

[gorenje]

That’s a nice offer but please be aware that I’ve already solved my requirements by using Erlang - Elixir bridge.

I’ve now moved on to CSV library!

[starbelly]

No worries It’s something I have to do anyway…

[mmzeeman]

@nzok

This is part of the reason why Butler Lampson, in his hints on system design, urged keeping interfaces small, advice I have ended up respecting every time I’ve ignored it.

My advisor at university always half jokingly asked: “Who doesn’t like an extended subset of features?”

[gorenje]

@mmzeeman

My advisor at university always half jokingly asked: “Who doesn’t like an extended subset of features?”

Just working on the CSV node - what a nightmare of extended superset of edge-cases disguised as features …

The great thing about Node-RED is that it does a lot of heavy lifting for common functionality, the bad thing is that it all needs to be implemented.

Markdown node was simple in comparison.

[jerome]

Hi, I had the same need, tried the same things. I ended up using pandoc-server.

[gorenje]

Thanks for the suggestion, but as I see it, that would require starting a haskell server alongside the Erlang-Red server. That would rather complicate the matter … And since the markdown node might or might not be utilised, this would further complicate the solution.