Skip to content

Releases: simon-the-shark/django-mapbox-location-field

Django 5.0+ update

18 Mar 23:36
Compare
Choose a tag to compare

There shouldn't be any breaking changes. Routine update, changed few details, fixed testing on github actions, upgraded bunch of versions etc.

Support for Django 3+

01 Mar 22:09
Compare
Choose a tag to compare

BREAKING CHANGES. Proper support for Django 3.x and 4.x. Thanks for #36 #35. Tests migrated to Github Actions.
Read more: https://github.com/simon-the-shark/django-mapbox-location-field#compatibility

https://pypi.org/project/django-mapbox-location-field/2.0.0/

Geocoding language feature

19 Apr 21:46
Compare
Choose a tag to compare

Introduced language and message_404 parameters in map_attrs options. Read more in documentation. Feature upon request #27

Fixed readonly and placeholder attributes

30 Jan 15:27
Compare
Choose a tag to compare

Admin customization fix

04 Dec 19:33
Compare
Choose a tag to compare

Finally a proper solution for #20 Proposed by @mjnaylor8 (#22)

Resolved #21

26 Oct 15:58
9d519cc
Compare
Choose a tag to compare

Resolved #21. Solution for the issue is presented in the troubleshooting section

admin integration fix

09 Aug 20:06
Compare
Choose a tag to compare

Fixed few bugs in admin panel integration (#19)

PlainLocationField fixed direct db saving

06 Jul 15:57
Compare
Choose a tag to compare

Issue #15. Now you can e.g. serialize this field with Django Rest Framework's CharField. Just remember about proper field validation or deal with a build-in db protection mechanism. (Read more #15 )

Added multiple fields possibility

03 Jul 22:07
Compare
Choose a tag to compare

Feature requested in the #13 issue. Added in cooperation with @edgaru (PR #14 )

Fix #10 issue

11 May 12:30
Compare
Choose a tag to compare

Just fixed the #10 issue, which is a major bug