| Age | Commit message (Collapse) | Author |
|---|
|
|
|
screens
|
|
|
|
space between the attributes
|
|
|
|
|
|
|
|
|
|
"or" and "and" datatypes
The commit adds a recursive parser for datatype expressions which allows nesting of validators,
this allows for complex expressions like "list(or(range(0,65535),'infinite'))" to allow a list of
values which are either integers between 0 and 65535 or the literal string "inifinite".
That change also deprecates combined datatypes like "ipaddr" ["or(ip4addr,ip6addr)"] or
"host" ["or(hostname,ip4addr,ip6addr)"]
|
|
can be represented with neg(type)
|
|
For SimpleSection, use the section name (always "1") instead of the
section type in the CBI-like string used to identify the upload. This
allows upload fields to be placed in SimpleSections. The fix changes a
minimal number of lines, but does introduce some unnecessary confusion,
it may or may not be better than a more thorough/invasive fix.
Set the enctype for the form element in the simpleform view to be
multipart/form-data because the default
application/x-www-form-urlencoded does not support input files.
Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
|
|
and allowlocal are enabled
|
|
|
|
|
|
|
|
notation
|
|
|
|
comboboxes
|
|
and dots
|
|
datatypes
|
|
|
|
|
|
|
|
|
|
ifattr() helpers (#10317)
|
|
|
|
them avilable to all templates, remove duplicate exports in cbi tempalte scope
|
|
for templates
|
|
redirects to the first child of a node, useful for menus that are empty by default and may gain arbritary childs
|
|
|
|
|
|
|
|
|
|
|
|
multiple, filtered TypedSection instances of the same type are used within a single Map
|
|
side validation in SimpleForm instances
|
|
|
|
|
|
|
|
|
|
update
|
|
|
|
control in form rendering
|
|
|
|
applications/luci-upnp: tune input class attributes
|
|
settings
|
|
all member ifaces in checkbox mode
|
|
"neg(hostname)" would allow "!example.com"
|
|
|
|
entries
|
