🎨 Breaking down Renderers → TemplateEngine + (Parser + Deserializer)

[YousefEZ]

The idea here is to allow the user to select which templating mechanism they want to use (e.g. Jinja2), and the compiler is the current renderer, which translates XML or JSON into a Embed object and/or view.

This is a diagram of the new process, perhaps a v2.0.0 release?

Update 1

Proposal has gone through. With some changes

The names have tweaked.

1. Compiler is decomposed into Parser, and Deserializer.
2. Parser is required to fetch the embed or menus, and deserializer converts the text/document into objects.
3. Renderer is now passed into the QalibContext rather than the QalibContext instantiating the Renderer, allowing for dependency injections and variants of Renderers.
4. There are RenderingOptions to control when and how the document is templated before being deserialized.

Instead of Qalib