#36411: get_preferred_type ignores params -------------------------------+-------------------------------------- Reporter: magicfelix | Owner: (none) Type: Bug | Status: new Component: HTTP handling | Version: 5.2 Severity: Normal | Resolution: Keywords: | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------+-------------------------------------- Comment (by Jake Howard):
I agree with Sarah that we should take into account the parameters (I'd not come across them before when I implemented this). The `q` param specifically will still need some special handling when it comes to ordering, as I think all other parameters should be considered exact matches rather than trying to parse version numbers from them. I believe the current implementation considers specificity in the ordering, but I may be wrong. Either way, we should make sure it's covered by tests! -- Ticket URL: <https://code.djangoproject.com/ticket/36411#comment:6> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/django-updates/0107019710c491bf-9406c3e3-9d46-40f0-b371-a20904edc12e-000000%40eu-central-1.amazonses.com.