Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update django-autocomplete-light to 2.3.3 #58

Merged
merged 1 commit into from
Jul 29, 2016

Conversation

pyup-bot
Copy link
Collaborator

There's a new version of django-autocomplete-light available.
You are currently using 2.2.10. I have updated it to 2.3.3

Changelog

2.3.3

  • 563 Don't disable multiplechoicewidgets if select is [multiple]
  • Don't import anything in init anymore if on django 1.9
  • test_project fixes, for the above.

2.3.2

2.3.1 Forgot the static files in 2.3.0.

2.3.0

  • 555 Django 1.4, 1.5 and 1.6 deprecation
  • 497 Enable registration by model-name by luzfcb
  • 536 551 Support proxy models by onrik
  • 553 improved jQuery integration by blueyed
  • 516 Corrected french transation by apinsard
  • 541 Use error_messages on FieldBase to allow overrides by dsanders11
  • 505 Ordering alias clash fix by sandroden
  • 515 Polish translation update by mpasternak
  • 543 ModelChoiceField requires the queryset argument
  • 494 ModelChoiceField Watch changes to 'queryset' by jonashaag
  • 514 Fixed deprecation warning on Django 1.8 by spookylukey
  • 498 548 improved i18n support
  • 547 prevents loading genericm2m if not in INSTALLED_APPS
  • JAL18 Fix: Get value.length while value is null by hongquan
  • JAL19 Clarify license by stevellis, all MIT
  • JAL17 Disable the widget input when it is not in use dsanders11
  • JAL15 Support openning results in new tab thebao
  • JAL14 Don't autohilight first choice by default pandabuilder
  • JAL13 Add option for box aligning with right edge of input dsanders11

IMPORTANT

536 At this point, proxy model support is untested, this is because I intend
to refactor the test suite and documentation during the 2.3.x serie.

494 Updating the queryset from outside the autocomplete class may lead to a
security problem, ie. if you don't replicate filters you apply manually on the
autocomplete object choices into choices_for_request() then a malicious user
could see choices which they shouldn't by querying the autocomplete directly.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 馃

@mention-bot
Copy link

@pyup-bot, thanks for your PR! By analyzing the annotation information on this pull request, we identified @ad-m and @requires to be potential reviewers

@coveralls
Copy link

coveralls commented Jul 29, 2016

Coverage Status

Coverage remained the same at 88.528% when pulling d4ff127 on pyup-update-django-autocomplete-light-2.2.10-to-2.3.3 into b59c9c6 on master.

@ad-m ad-m merged commit b00c933 into master Jul 29, 2016
@ad-m ad-m deleted the pyup-update-django-autocomplete-light-2.2.10-to-2.3.3 branch August 22, 2016 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants