Multiple function files

[EvaluationContext]

Support for n number of function.tmdl files, at least for medium + libraries.

More flexible library structure. Provides better experience for LLM and Developers.

GitHub action to union tmdl files. Optional: Support for nested directory of TMDL files

[albertospelta]

Thanks @EvaluationContext, great suggestion and definitely a needed feature. I’ll move this to https://github.com/daxlib/lib-quickstart-template so merging multiple functions.tmdl files can be implemented directly in the publish workflow. Thanks again!

[albertospelta]

Hi @EvaluationContext,

I've added support for multi-file TMDL layout to the publish workflow in the DaxLib.SVG repos.
Here's how it works — there are now two ways to organize DAX function definitions, and they can be used together:

• Single file (lib/functions.tmdl) — works exactly as before, nothing changes.
• Functions folder (lib/functions/) — functions can be split across multiple .tmdl files, with optional subdirectories. The folder structure is flexible.

At publish time, the workflow uses functions.tmdl as the base (if present) and appends all .tmdl files found in the functions/ folder, sorted by path for deterministic output. The folder is then removed from the package, so the published output is always a single functions.tmdl.

I'm starting with DaxLib.SVG since it's complex enough to be a good test case. Once validated, I'll update the other DaxLib repos and the lib-quickstart-template as well.

When you get a chance, could you take a look (see daxlib/dev-daxlib-svg#18) and let me know if everything looks good?
Thanks!

[EvaluationContext]

Cool, I'll give it a try