Opened 9 years ago

Closed 9 years ago

#3598 closed (fixed)

URL dispatch docs clairification, optional dictionary precedence

Reported by: yary h <nospam@…> Owned by: adrian
Component: Core (Other) Version: master
Severity: Keywords: URL dispatch
Cc:… Triage Stage: Ready for checkin
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


I had a URL pattern like so:

r('^test/(?<foo>w+)?','test_view',{'foo':'there is no foo!'})

It's a case that's not covered in the documentation. It looks like the optional dictionary overrides the passed in URL, which isn't what I expect, but as an undocumented case with an easy work around, I can live with it.

Think about how above pattern should behave, check that it does it, and document!


Attachments (1)

3598.diff (706 bytes) - added by ubernostrum 9 years ago.
Documentation patch

Download all attachments as: .zip

Change History (3)

Changed 9 years ago by ubernostrum

Documentation patch

comment:1 Changed 9 years ago by ubernostrum

  • Component changed from Uncategorized to Core framework
  • Needs documentation unset
  • Needs tests unset
  • Owner changed from jacob to adrian
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Ready for checkin

comment:2 Changed 9 years ago by jacob

  • Resolution set to fixed
  • Status changed from new to closed

(In [4638]) Fixed #3598: Added a note about the precedence of URL matches versus extra kwargs in URL patterns. Thanks, Ubernostrum.

Note: See TracTickets for help on using tickets.
Back to Top