Opened 8 years ago

Closed 8 years ago

#2224 defect closed invalid (invalid)

Web2: Behavior of Request.locateResource vs Resource.locateChild is not clearly defined.

Reported by: dreid Owned by:
Priority: high Milestone:
Component: web2 Keywords:
Cc: dreid Branch:
Author: Launchpad Bug:

Description

Several issues exist. Most notably the dependency between locateResource and locateChild is unclear. Also what happens when urlForResource is called with a resource that wasn't "located" in via one of these methods.

Change History (2)

comment:1 Changed 8 years ago by wsanchez

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

Don't assign a bug to me referencing "several issues" unless you have itemized all of them, eh? I'm not a mind reader.

locateResource and locateChild are different methods. locateResource has a docstring that tells you what it does.

urlForResource also has a docstring that tells you what happens with a resource wasn't "located": it returns None. I'm starting to think it should raise an Exception instead, which is more in line with KeyError from a dictionary.

comment:2 Changed 4 years ago by <automation>

  • Owner wsanchez deleted
Note: See TracTickets for help on using tickets.