Opened 17 years ago

Closed 17 years ago

#3598 closed (fixed)

URL dispatch docs clairification, optional dictionary precedence

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

Description

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!

thanks

Attachments (1)

3598.diff​ (706 bytes ) - added by James Bennett 17 years ago.
Documentation patch

Download all attachments as: .zip

Change History (3)

by James Bennett, 17 years ago

Attachment: 3598.diff​ added

Documentation patch

comment:1 by James Bennett, 17 years ago

Component: Uncategorized → Core framework
Owner: changed from Jacob to Adrian Holovaty
Triage Stage: Unreviewed → Ready for checkin

comment:2 by Jacob, 17 years ago

Resolution: → fixed
Status: new → 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