Opened 13 years ago

Last modified 10 years ago

#2094 enhancement new

URLPath should provide an API for manipulating query arguments

Reported by: David Reid Owned by: David Reid
Priority: normal Milestone:
Component: core Keywords:
Cc: oubiwann, David Reid Branch:


For URLPath to make sense in #1569 applications need to be able to easily get specific query arguments and for the client to modify them.

Change History (2)

comment:1 Changed 13 years ago by oubiwann

Cc: oubiwann David Reid added

What is the preferred means of getting the specific query arguements? I.e., How does IRequest want to use this? In the second class of this recipe:

a dictionary (and then some) is used.

There is already a query attribute on URLPath. Would you like to add a method such as URLPath.parseQuery() that instantiates a new class, URLQuery, parses it, and returns a dict? Or would you like a new attribute, maybe .parsedQuery that is a dict?

comment:2 Changed 10 years ago by Glyph

Owner: changed from Glyph to David Reid

I really want nevow.url, or something like it, to be in twisted.web somewhere. This strikes me as potentially redundant with that.

Note: See TracTickets for help on using tickets.