Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Use a real template enginge (e.g. liquid) instead of home grown .create.template Files #51

Open
hf-kklein opened this issue Jun 1, 2022 · 1 comment

Comments

@hf-kklein
Copy link
Contributor

Our homegrown, edifact format specific .create.template files (example) are:

  • not automatically checked yet (and they do have some errors)
  • not parsable except by the edilibrary here

If we used a real template engine (e.g. Jinja), we could make use of all the tooling and ecosystem around it and e.g.

  • write edifact automation in any langauge
  • have builtin compile time consistency and syntax checks

Credits for this idea @hf-krechan

@hf-kklein
Copy link
Contributor Author

Idea is to use liquid because it has the broadest tooling available and allows for evolution instead of revolution.
https://github.com/Shopify/liquid/wiki/Ports-of-Liquid-to-other-environments

@hf-kklein hf-kklein changed the title Use a real template enginge instead of home grown .create.template Files Use a real template enginge (e.g. liquid) instead of home grown .create.template Files Jan 9, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant