| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
method
|
| |
|
|
|
|
|
|
|
| |
traceback)
This is awkward but there?s currently no better way to do this, short of
dynamically generating the entire form each time
|
|
|
|
|
| |
The receiving end presumably already have the original form, so these
potentially long text fields are of little value.
|
|
|
|
|
|
|
|
|
|
|
| |
XEP-0004 says:
> a data form of type "cancel" SHOULD NOT contain any <field/> elements.
The title and instructions don't seem to be of much value in this case
either.
I'm not aware of 'cancel' being used anywhere, so this should break
nothing. Early return is always nice.
|
|
|
|
| |
Options should not be needed in other types of forms.
|
| |
|
| |
|
|
|
|
| |
traceback, thanks Martin)
|
|
|
|
|
| |
Ensure that a non-nil data[field_name] always overrides the field's default,
and that values of boolean 'false' are always rendered in the form.
|
| |
|
|
|
|
|
| |
This is meant to allow identifying forms without parsing them
completely.
|
| |
|
| |
|
| |
|
|
|
|
| |
field.value[].default
|
| |
|
| |
|
|
|
|
| |
(fixes #521)
|
|
|
|
| |
duplicate code
|
|
|
|
| |
return them in a table at the end
|
| |
|
| |
|
|\ |
|
| | |
|
|\| |
|
| | |
|
|/ |
|
|
|
|
| |
with other readers
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
from Florob
|
|
|
|
| |
input data
|
| |
|
| |
|
| |
|