Update dependency django-phonenumber-field to v7
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
django-phonenumber-field | dependencies | major |
^6.1 -> ^7.0
|
Release Notes
stefanfoulis/django-phonenumber-field
v7.0.2
What's Changed
- Updated Swedish translations by @tjwalch in https://github.com/stefanfoulis/django-phonenumber-field/pull/544
New Contributors
- @tjwalch made their first contribution in https://github.com/stefanfoulis/django-phonenumber-field/pull/544
Full Changelog: https://github.com/stefanfoulis/django-phonenumber-field/compare/7.0.1...7.0.2
v7.0.1
What's Changed
- Allow multiple DRF is_valid calls to succeed by @phillipuniverse in https://github.com/stefanfoulis/django-phonenumber-field/pull/543
New Contributors
- @phillipuniverse made their first contribution in https://github.com/stefanfoulis/django-phonenumber-field/pull/543
Full Changelog: https://github.com/stefanfoulis/django-phonenumber-field/compare/7.0.0...7.0.1
v7.0.0
Possible backward incompatibilities
-
RegionalPhoneNumberWidget
becomes the default widget for theformfields.PhoneNumberField
. - The
formfields.PhoneNumberField
no longer sets theinput_type
attribute of its widget totel
. That behavior did not make sense for the existingPhoneNumberPrefixWidget
and was dropped. -
PhoneNumberInternationalFallbackWidget
will be replaced byRegionalPhoneNumberWidget
in the next major version. It is deprecated until the next major release.
Changes
-
Restore
PhoneNumberPrefixWidget
number input on form errors by @francoisfreitag in https://github.com/stefanfoulis/django-phonenumber-field/pull/520Fixes a bug where the form field
prepare_value()
transformed thePhoneNumber
value to anstr
in the national format, butPhoneNumberPrefixWidget
expects its value to be aPhoneNumber
.formfields.PhoneNumberField
now represents its value with aPhoneNumber
object, giving widgets more control on how to display the value.That behavior prompted the change to
PhoneNumberInternationalFallbackWidget
becoming the default widget, to preserve the behavior established in https://github.com/stefanfoulis/django-phonenumber-field/commit/005769cf39323e5b23710783f45befb546672cd6. Switching to the widget allows users to opt-out from that behavior (e.g. by using aTextInput
widget), whereasprepare_value()
forced the conversion to the national string format. -
Set
PhoneNumberInternationalFallbackWidget
input_type
totel
by @francoisfreitag in https://github.com/stefanfoulis/django-phonenumber-field/pull/521Previously, the
<input>
from thePhoneNumberInternationalFallbackWidget
was set totext
. -
Evolve
PhoneNumberInternationalWidget
toRegionalPhoneNumberWidget
by @francoisfreitag in https://github.com/stefanfoulis/django-phonenumber-field/pull/529The newer widget gives more control over the display of phone numbers. The behavior of
PhoneNumberInternaltionalWidget
can be retained by settingPHONENUMBER_DEFAULT_FORMAT="INTERNATIONAL"
, which is whyPhoneNumberInternaltionalWidget
will be removed in the next major version. -
Add Dutch translation by @thijskramer in https://github.com/stefanfoulis/django-phonenumber-field/pull/532
-
Add documentation and host it at readthedocs.org by @francoisfreitag in https://github.com/stefanfoulis/django-phonenumber-field/pull/531
-
Prefer
SUPPORTED_REGIONS
over_AVAILABLE_REGION_CODES
by @francoisfreitag in https://github.com/stefanfoulis/django-phonenumber-field/pull/528
New Contributors
- @thijskramer made their first contribution in https://github.com/stefanfoulis/django-phonenumber-field/pull/532
Full Changelog: https://github.com/stefanfoulis/django-phonenumber-field/compare/6.4.0...7.0.0
Configuration
-
If you want to rebase/retry this MR, click this checkbox.
This MR has been generated by Renovate Bot.