* needs_better_patch: 0 => 1
* easy: => 0
Comment:
options.py.diff fails to apply cleanly on to trunk
--
Ticket URL: <http://code.djangoproject.com/ticket/13883#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by rynomster):
Did this change ever make it to trunk?
I can't seem to find it.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:10>
Comment (by timgraham):
No, the ticket is still open. It doesn't appear we have a tested patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:11>
* cc: Narbonne (added)
* version: 1.2 => master
* type: Bug => New feature
Comment:
subscribing too. a bit sad to see the feature I was looking for in an
abandoned old ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:12>
* type: New feature => Bug
Comment:
Hello Narbonne,
I get your feeling about discovering a still unsolved long standing issue.
Most of Django contributors are volunteers though and issues only get
fixed if someone commits to spend a part of their limited amount of time
to submitting a patch and testing it. Given this issue hasn't received a
lot of attention in the past years I assume it wasn't critical enough for
someone to some of their time to it.
If it is to you I'd encourage you to go through the
[https://docs.djangoproject.com/en/2.1/internals/contributing/
contributing guide] and try to revive the previous patch. From a quick
look it seems like adding `optgroup` support to `SelectBox.js` and adding
a `group_by` option to `ModelChoiceField` à la #27331.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:13>
* owner: nobody => Jignesh Kotadiya
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:14>
* cc: Jignesh Kotadiya (added)
* easy: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:15>
Comment (by Jignesh Kotadiya):
[https://github.com/django/django/pull/12737]
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:16>
* owner: Nishant Sagar => Abhiraj Chatterjee
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:18>
Comment (by Marius Räsener):
Hello everybody,
I'm trying to contribute to Django with this "easy picking" issue. The PR
on Github was closed by Jignesh Kotadiya and currently the PR says
`jigneshkotadiya000 wants to merge 0 commits into 'django:master' from
'unknown repository'` - so I'm already stuck I guess.
Is this still issue still open? If yes, should I give it a try?
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:19>
Comment (by ᴙɘɘᴙgYmɘᴙɘj):
Here's a [minimal repro](https://github.com/reergymerej/ticket_13883) for
anyone who is interested.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:20>
* owner: Abhiraj Chatterjee => (none)
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:21>
* Attachment "13883-fix.patch" added.
Patch to retain option groups, and test
--
Ticket URL: <https://code.djangoproject.com/ticket/13883>
Comment (by Mariusz Felisiak):
Thanks, please send [https://github.com/django/django/pulls PR via
GitHub].
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:22>
Old description:
> Current implementation ignores optgroup elements in selects. Here is an
> example of SelectBox.js which takes optgroups in account, but uses jQuery
> (already used by django admin anyway).
> The script is not perfectly written. I can rewrite this to meet django's
> coding/quality standards if needed.
New description:
--
Comment (by Narbonne):
I don't see an update of the filter method. I suppose search should also
search in the optgroup name (a bit like sort before token search).
I update your patch line 45 in filter:
{{{
const node_text = (node.group && node.group.toLowerCase() || '') +
node.text.toLowerCase();
}}}
Also, maybe it could make sense to move optgroup as a block.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:23>
Comment (by Michael McLarnon):
Created PR: https://github.com/django/django/pull/15568
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:24>
* cc: Michael McLarnon (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:25>
* owner: (none) => Michael McLarnon
* needs_better_patch: 1 => 0
* status: new => assigned
Comment:
[https://github.com/django/django/pull/15568 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:26>
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:27>
* needs_better_patch: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:28>
* needs_tests: 1 => 0
Comment:
The PR author reported that the PR is ready for re-review, so I'm clearing
the flags.
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:29>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:30>
Comment (by rzrwolf):
13 years to fix the issue...
What is current status? Any beta that can be used, please?
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:31>
Comment (by Mariusz Felisiak):
Replying to [comment:31 rzrwolf]:
> 13 years to fix the issue...
>
> What is current status? Any beta that can be used, please?
This is an open-source, these kind of comments are unhelpful. Feel-free to
prepare a patch, or test [https://github.com/django/django/pull/15568 PR].
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:32>