• last updated 9 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
improve spelling

validate format of richtext field always

Smartify idioms

Fix typo

simplify idioms

Deprecate template::util::list_opts: it can be replaced by trivial tcl idioms

Streamline ns_set idioms

Deprecate template::util::set_to_vars: it can be replaced with trivial idioms

Deprecate template::util::set_to_list: this proc can be replaced with trivial ns_set and tcl idioms

Replace trivial api

Streamline ns_set idioms

  1. … 1 more file in changeset.
Uniform documentation style

Normalize indentation

Streamline ns_set idioms

Deprecate util_ns_set_to_list: ns_set array is an equivalent oneliner

  1. … 5 more files in changeset.
support multi-line messages by using template literals

template literals are available since ES6 (2015)

fix spurious colons

  1. … 4 more files in changeset.
improve safety of SQL queries

  1. … 2 more files in changeset.
added a "-verbose" flag to template::themed_template and template::resource_path to ease debugging

  1. … 1 more file in changeset.
Fix order in expression

Reduce divergency between oracle and postgres codebase

  1. … 3 more files in changeset.
improve spelling

  1. … 40 more files in changeset.
Enable to attach handlers by CSS selector also for template::add_confirm_handler

Port of downstream modification: apply trimming of zeros to all fields in advance

This allows to treat fields as real numbers without the need to trim case by case. One can also reduce dependency to api and just use plain tcl expressions to evaluate conditions

Port of downstream HTML5 date and time form widgets by Günter Ernst

These widgets provide a better and more consistent user experience and client-side validation across multiple platforms. They should in time become the preferred alternative for dates and time for template forms.

  1. … 2 more files in changeset.
Comment noop result of a 18 years old typo, add remarks

Arrays might or not have been a better choice for the date object, however, such decision happened very long ago and it has worked good enough... cleanup concerning remarks

Whitespace change

Review concerning remark: the algotirhm is indeed correct, assuming the year is expressed in the Gregorian calendar

Replace deprecated idiom