#27262: Delegate URL resolver checks to URL classes --------------------------------------+------------------------------------ Reporter: Sjoerd Job Postmus | Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (URLs) | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 1 | UI/UX: 0 --------------------------------------+------------------------------------
Comment (by Lucas Lois): I would like to implement this, if possible. What I thought about, and gathered form the linked post by Sjoerd Job, was transforming the check_resolver function into, basically, a simple loop callign `pattern.check()` and adding together all warnings. If I understand correctly, `check_*(pattern)` should become members of their respective classes (either `RegexURLResolver` or `RegexURLPattern`) and called directly by `check()` Could I be assigned this task? Is there anything I haven't thought about? Keep in mind I haven't commenced the implementation yet, just thought about it. -- Ticket URL: <https://code.djangoproject.com/ticket/27262#comment:3> 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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.dbfba0e0f93389c9125bdd5eed935a6b%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.