| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
conditional expressions.
|
|
|
|
|
|
|
| |
without "for"
Thanks Denis Martinez for the report and initial patch, and
Sergey Kolosov for bringing the patch up to date.
|
|
|
|
|
| |
In _get_changed_data, check if initial_value is a callable and call it
if it is.
|
|
|
|
| |
Gives much nicer errors when it fails.
|
|
|
|
| |
validating max_num.
|
|\
| |
| | |
Fixed #11160: Formset non_form_errors returns ErrorList() if is_valid is not called
|
| |
| |
| |
| |
| |
| |
| | |
non_form_errors
Updated FormSet.non_form_errors() to ensure full_clean() has
been called before returning the errors.
|
| |
| |
| |
| | |
max_length/min_length are integers
|
|/ |
|
|
|
|
|
|
|
|
| |
'exclude', and added '__all__' shortcut
This also updates all dependent functionality, including modelform_factory
and modelformset_factory, and the generic views `ModelFormMixin`,
`CreateView` and `UpdateView` which gain a new `fields` attribute.
|
| |
|
|
|
|
|
|
| |
error messages
Also fixed plural messages for DecimalField.
|
|
|
|
|
|
|
|
|
|
|
| |
RadioSelect
I refactored RadioSelect and CheckboxSelectMultiple to
make them inherit from a base class, allowing them to share
the behavior of being able to iterate over their subwidgets.
Thanks to Matt McClanahan for the initial patch and to
Claude Paroz for the review.
|
|
|
|
| |
RadioSelect
|
|
|
|
| |
CheckboxSelectMultiple
|
| |
|
|
|
|
|
|
|
| |
BoundField.label_tag
Also cleaned up label escaping and consolidated the test suite regarding
label_tag.
|
|
|
|
| |
for test discovery.
|
|
|
|
|
|
|
| |
arguments
In any case, setting those variables to non-ascii utf-8 bytestrings
is now considered a programming error.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
max_num on server.
This is provided as a new "validate_max" formset_factory option defaulting to
False, since the non-validating behavior of max_num is longstanding, and there
is certainly code relying on it. (In fact, even the Django admin relies on it
for the case where there are more existing inlines than the given max_num). It
may be that at some point we want to deprecate validate_max=False and
eventually remove the option, but this commit takes no steps in that direction.
This also fixes the DoS-prevention absolute_max enforcement so that it causes a
form validation error rather than an IndexError, and ensures that absolute_max
is always 1000 more than max_num, to prevent surprising changes in behavior
with max_num close to absolute_max.
Lastly, this commit fixes the previous inconsistency between a regular formset
and a model formset in the precedence of max_num and initial data. Previously
in a regular formset, if the provided initial data was longer than max_num, it
was truncated; in a model formset, all initial forms would be displayed
regardless of max_num. Now regular formsets are the same as model formsets; all
initial forms are displayed, even if more than max_num. (But if validate_max is
True, submitting these forms will result in a "too many forms" validation
error!) This combination of behaviors was chosen to keep the max_num validation
simple and consistent, and avoid silent data loss due to truncation of initial
data.
Thanks to Preston for discussion of the design choices.
|
| |
|
|
|
|
|
| |
When the 'invalid' error message is set at field level, it masks
the error message raised by the validator, if any.
|
|
|
|
|
|
|
| |
required TypedChoiceFields
Thanks Florian Apolloner for the report and the review.
Also fixes #19643.
|
|
|
|
|
| |
Tests that require USE_I18N, LOGIN_URL or certain MIDDLEWARE_CLASSES
should be decorated appropriately.
|
|
|
|
|
| |
Thanks Loic Bistuer for spotting the regression and the initial
patch. Refs #16612.
|
|
|
|
| |
Thanks Loic Bistuer for the report and the patch.
|
| |
|
|
|
|
|
|
| |
TIME_INPUT_FORMATS
Thanks minddust for the report.
|
|
|
|
|
|
| |
localized field values
Thanks Simon Charette for the review.
|
| |
|
|
modeltests/regressiontests.
|