#2248: tg.url() behaves differently than pylons.url()
-------------------------------+--------------------------------------------
Reporter: Federico2 | Owner:
Type: defect | Status: new
Priority: normal | Milestone: 2.0
Component: TurboGears | Version: 2.0b5
Severity: normal | Resolution:
Keywords: tg.url pylons.url |
-------------------------------+--------------------------------------------
Comment (by jorge.vargas):
Here is my take on what this api should be.
{{{
tg.url() -> current path
tg.url('') -> ?
tg.url('/') -> /
tg.url('/something') -> /something
tg.url(list) -> /elem1/elem2/....
tg.url('',some=thing) -> ?some=thing
tg.url('',some=thing,other=thing) -> ?some=thing&other=thing
tg.url('/p',some=thing) -> /p?some=thing
tg.url('p',some=thing,other=thing) -> p?some=thing&other=thing
tg.url(action='update') -> routes
}}}
Does that makes sense? will it please everyone?
--
Ticket URL: <http://trac.turbogears.org/ticket/2248#comment:1>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
