Switch from EJS templates to Unist-Builder?

[trieloff]

Looking at issues like #91, #112 and #118 and considering the considerable amount of logic that would seep back into our templates, I'm wondering if we should switch to something like https://github.com/syntax-tree/unist-builder to create proper Markdown Abstract Syntax Trees, which would enable us to modularize the code, add more granular unit tests and even support different output flavors.

[Relequestual]

This looks like an interesting approach. Is there a demo somewhere of how it can be used to construct an AST and turn it into markdown?

[trieloff]

I could build a POC PR for the Readme page.

[Relequestual]

Happy to take a look at such! =]

[Claymore1337]

@trieloff
I have created a feature where a user could provide a list of attributes that should also be displayed into the property discription. For example you call the generater with this two fileds "version,task" the result will looked like this for a property.

ehepartnerId

Define which static id should be used

ehepartnerId

• is required
• type: string
• default: ""
• defined in this schema
• version: 1.28.0
• task: P-100

ehepartnerId Type

string

All instances must conform to this regular expression

^(.*)$

• test example: ehepartner

ehepartnerId Example

"ehepartner"

Does it make sence to provide a merge request or will this feature be pointless with the Unist-builder?

[trieloff]

It makes sense to create a PR, don't feel held back by ideas that I don't have time for to implement ;)

[trieloff]

🎉 This issue has been resolved in version 4.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀