Introduce dynamic scope_path regexps Instead of relying on scope_path's being "one slash deep", we should instead allow for either: 1. scope_paths that have a pre-defined depth 2. scope_paths that can be arbitrarily deep We achieve 1 by setting an entities scope_logic to another logic module. We then recursively call getScopeDepth until we get to the topmost entity (that is, an unscoped entity). A little different is the solution to 2, since some entities can have an arbitrarily deep scope (such as Documents), we need to have some way of signaling this to getScopePattern. A clean solution is to return None, rather than a number. If None is returned, the SCOPE_PATH_ARG_PATTERN is returned as regexp instead, which will match an arbitrarily deeply nested scope. The solution for 2 requires that we return None somewhere in the scope_logic chain, the most straight forward method to do so is to override getScopeDepth anywhere such a scope is needed and make it return None. A more elegant solution however, is to set the scope_logic to that module in all entities that require it. Patch by: Sverre Rabbelier

     1

# Please sort this file in alphabetical order by last (given) name.

     2

# Please only include one name per line.  If an (optional) email address is

     3

# included, it must be RFC 2821 compliant (properly quoted, escaped, etc.).

     4

# Lines beginning with # can be stripped from the file, as can blank lines.

     5

     6

"Todd Larsen" <tlarsen@google.com>

     7

"Chen Lunpeng" <forever.clp@gmail.com>

     8

"Sverre Rabbelier" <sverre@rabbelier.nl>

     9

"Lennard de Rijk" <ljvderijk@gmail.com>

    10

"Pawel Solyga" <pawel.solyga@gmail.com>