Allow a subordinate entry resource under a resource where there would normally be a field

AFIACT, this is already supported. You just have to make sure that the web application can traverse to <branch>/code_import. Field navigation only kicks in after the regular web application traversal has taken place.

So adding the proper navigation to Branch to get to code_import would be work.

This already works, if you have the navigation for it. The problem that led me to file this bug was a lack of navigation.

I'm uninvalidating this because I'm having exactly the same problem. Mailing lists are subordinate to teams, so it makes sense to access them through ~myteam/mailing_list. But this only returns that url back to me and I cannot get a MailingList as an entry, which is really what I want.

I do not want to expose mailing list properties on the IPerson, so I need to fix this.

Bug 385180 is blocked on this.

So, I'm having a very difficult time creating a lazr.restful test for this problem. I have a test case and a code fix for Launchpad, but I'm in a twisty maze of hurt trying to reproduce the problem in lazr.restful itself.

What I have so far: lp:~barry/lazr.restful.387487-subordinate

but it sucks :(

However, in src/lazr/restful/publisher.py, the following code fixes the
problem:

    def traverseName(self, request, ob, name):
        """See `zope.publisher.interfaces.IPublication`.

        In addition to the default traversal implementation, this publication
        also handles traversal to collection scoped into an entry.
        """
        # If this is the last traversal step, then look first for a scoped
        # collection. This is done because although Navigation handles
        # traversal to entries in a scoped collection, they don't usually
        # handle traversing to the scoped collection itself.
        if len(request.getTraversalStack()) == 0:
            try:
                entry = IEntry(ob)
            except TypeError:
                pass
            else:
                field = entry.schema.get(name)
                if ICollectionField.providedBy(field):
                    result = self._traverseToScopedCollection(
                        request, entry, field, name)
                    if result is not None:
                        return result
                elif IBytes.providedBy(field):
                    return self._traverseToByteStorage(
                        request, entry, field, name)
                elif IObject.providedBy(field):
                    sub_entry = getattr(entry, name, None)
                    if sub_entry is None:
                        raise NotFound(ob, name, request)
                    else:
                        return sub_entry
                elif field is not None:
                    return EntryField(entry, field, name)
                else:
                    # Falls through to our parent version.
                    pass
        return super(WebServicePublicationMixin, self).traverseName(
            request, ob, name)

Note the new goodness in the "elif IObject" stanza.

On Fri, 2009-07-24 at 15:46 +0000, Barry Warsaw wrote:
> So, I'm having a very difficult time creating a lazr.restful test for
> this problem. I have a test case and a code fix for Launchpad, but I'm
> in a twisty maze of hurt trying to reproduce the problem in lazr.restful
> itself.
>
> What I have so far: lp:~barry/lazr.restful.387487-subordinate
>
> but it sucks :(
>
> However, in src/lazr/restful/publisher.py, the following code fixes the
> problem:
>
> def traverseName(self, request, ob, name):
...
> elif IObject.providedBy(field):
> sub_entry = getattr(entry, name, None)
> if sub_entry is None:
> raise NotFound(ob, name, request)
> else:
> return sub_entry
...

I think you want to update WadlAPITestCase to add a suborinate interface
to verify the wadl is correct.

Travering is tested in doc/webservice.txt. I think you want to add a
subordinate object to the test objects (ingredient, instructions,
wine_pairing). There is some URL tests that verify objects are found.
These tests deal with PATCH, but GET can be added.