Hopiu/django-select2
1
0
Fork 0
mirror of https://github.com/Hopiu/django-select2.git synced 2026-03-16 21:40:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #177 from blueyed/doc-fixes

Browse source 
doc: fix typos/grammar
This commit is contained in:
Johannes Hoppe 2015-06-08 14:54:47 +02:00
commit 1d49045477
2 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
django_select2/__init__.py
View file

@ -29,8 +29,8 @@ Widgets are generally of two types :-
so you need not worry about writing any Ajax related JS code. Although on the server side you do need to
create a view specifically to respond to the queries.
Heavies have further specialized versions called -- **Auto Heavy**. These do not require views to server Ajax
request. When they are instantiated, they register themselves with one central view which handles Ajax requests
Heavies have further specialized versions called -- **Auto Heavy**. These do not require views to serve Ajax
requests. When they are instantiated, they register themselves with one central view which handles Ajax requests
for them.
Heavy widgets have the word 'Heavy' in their name. Light widgets are normally named, i.e. there is no 'Light' word

10
django_select2/widgets.py
View file

@ -85,9 +85,9 @@ class Select2Mixin(object):
.. tip:: You cannot introduce new options using this. For that you should sub-class and override
:py:meth:`.init_options`. The reason for this is, few options are not compatible with each other
or are not applicable in some scenarios. For example, when Select2 is attached to ``<select>`` tag,
it can get if it is multiple or single valued from that tag itself. In this case if you specify
``multiple`` option then not only it is useless but an error in Select2 JS' point of view.
or are not applicable in some scenarios. For example, when Select2 is attached to a ``<select>`` tag,
it can detect if it is being used with a single or multiple values from that tag itself. If you specified the
``multiple`` option in this case, it would not only be useless but an error from Select2 JS' point of view.
There are other such intricacies, based on which some options are removed. By enforcing this
restriction we make sure to not break the code by passing some wrong concoction of options.
@ -344,10 +344,10 @@ class HeavySelect2Mixin(Select2Mixin):
:param data_url: Url which will respond to Ajax queries with JSON object.
:type data_url: :py:obj:`str` or None
.. tip:: When ``data_view`` is provided then it is converted into Url using
.. tip:: When ``data_view`` is provided then it is converted into an URL using
:py:func:`~django.core.urlresolvers.reverse`.
.. warning:: Either of ``data_view`` or ``data_url`` must be specified, else :py:exc:`ValueError` would
.. warning:: Either of ``data_view`` or ``data_url`` must be specified, otherwise :py:exc:`ValueError` will
be raised.
:param choices: The list of available choices. If not provided then empty list is used instead. It