Release 5.0.1 - New multi-module architecture
· One min read
Starting with version 5, the Java and Kotlin APIs are provided in separate modules.
As a result, the core Java HtmlFlow module no longer depends on the Kotlin coroutines library or jsoup (which is now only required by the reverse-engineering tool Flowifier, moved to its own module).
HtmlFlow is now organized into four distinct modules:
- htmlflow-core: The main library (the
htmlflowartifact) containing the Java API. - flowifier: A reverse-engineering tool for translating HTML documents into equivalent HtmlFlow view definitions.
- htmlflow-kotlin: The idiomatic Kotlin API (which depends on
htmlflow-core). - htmlflow-view-loader: A reflective inspector for HtmlFlow view definitions. It loads Kotlin functions of type
T -> Stringthat return rendered HTML.
tip
The htmlflow-view-loader module is particularly useful for integrating with web servers like http4k, which treat render engines as T -> String functions.
Additionally, an mfe() builder has been added to dynamically load HTML fragments, supporting both SSR and CSR approaches within HtmlFlow view definitions.