Next major version #17

BREAKING CHANGES $templates:lookup-param-from-restserver is now a sequence of functions of arity 1

Error reporting: When a template function is not defined the error message will include the serialized node to help users figure out where the problem occurs. Ensure configuration is present in $model: Before, each time the configuration was retrieved it was first checked if it was present. This check is now moved to the places where users are able to modify the model and thus may remove it from the map. - add a new private function templates:process-children - templates:process will now check for the configuration to be present - now that the presence of configuration is ensured `templates:get-configuration` is no longer necessary as this can be expressed with a simple map lookup

Each case is now a private function of its own (form, input, select).

- refactor initial functions - templates:apply#3 and eXist-db#4 - templates:render#3 - add function templates:configure called in all initial functions - attribute filtering function is now selected by configuration instead main benefit is the if condition does not need to be called each time

- lib:include moved to templates:include - lib:parse-params is now moved to templates:parse-params - remove lib - last remaining lib function lib:resolve-apps is now apps:by-abbrev links are now added to the model under key 'app' declare default value for links of apps that were not found - delimiters are now part of the configuration and cannot be changed inside of templates - add example (and test) for reading template-path from model - refactor for speed and readability

- the default handling of duplicates when merging maps will change to use-first. Therefore set duplicate handling explicitly to use-last where it is crucial

This is the first version that implements map:merge#2

BREAKING CHANGES: - $templates:START_DELIMITER => $templates:CONFIG_START_DELIMITER - $templates:END_DELIMITER => $templates:CONFIG_END_DELIMITER - All errors are prefixed with E_ - All settings are prefixed with CONFIG_

In an effort to declare all dependencies explicitly.

- add comment if surround template was not found - avoid *-selector in XPath expression

Simplify check for problematic options.

The $selected variable either contains the attribute setting an option as selected or an empty sequence.

This is in order to drop them from being the default in the next step.

- apps is now tmpl-apps to make it obvious it is not an application module - tmpl-util contains utility functions that clobber up the core library (unused for the moment)

- build regular expressions for parse-params at configuration and re-use those throughout the code base - remove functions from template that are now in tmpl-util - use tmpl-util:* replacements in templates functions

This deprecates templates:parse-params as placeholders in text and attribute nodes will always be replaced. Before: `<span data-template="templates:parse-params">[[item]]</span>` Now : `<span>[[item]]</span>` Any data-template attribute with the value "templates:parse-params" is ignored.

Always throw an error if a declared template function cannot be found. The attempt to ignore certain function names creates more problems than it solves as it does not incentivise to clean up templates when switching to the newer templating library. The test for templates with a legcacy declaration was apapted.

eXist-db will now return status code 500 server error when an exeption is thrown during query execution (see eXist-db/exist#4639). Since the templating library is not concerned with routing we simply add this other accepted status code to the list. Tests expecting errors will pass with both satus code 400 and 500.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Next major version #17

Next major version #17

Commits on Jul 18, 2023

Next major version #17

Are you sure you want to change the base?

Next major version #17

Commits on Jul 18, 2023