Merge lp:~rockstar/launchpad/no-recipes-on-private-branches into lp:launchpad
Proposed by
Paul Hummer
Status: | Merged |
---|---|
Approved by: | Curtis Hovey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 11362 |
Proposed branch: | lp:~rockstar/launchpad/no-recipes-on-private-branches |
Merge into: | lp:launchpad |
Diff against target: |
49 lines (+18/-3) 2 files modified
lib/lp/code/browser/branch.py (+6/-3) lib/lp/code/browser/tests/test_sourcepackagerecipe.py (+12/-0) |
To merge this branch: | bzr merge lp:~rockstar/launchpad/no-recipes-on-private-branches |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Curtis Hovey (community) | code | Approve | |
Review via email: mp+32799@code.launchpad.net |
Description of the change
This branch fixes bug #612567 - It doesn't show the "Create recipe" link on private branches.
To post a comment you must log in.
I would have used person( self.chef) logged_ in(self. chef):
login_
or removed the need for logout using
with person_
Also you changed the menu, but test the template; I would have tested the view. I was puzzled and saw in the templates:
<span define= "link context_ menu/create_ recipe" condition= "link/enabled" replace= "structure link/render"
tal:
tal:
tal:
/>
That is odd, because I think we have a safty net in the formatters for this that ensure a disabled link is never rendered:
<a tal:replace= "context_ menu/create_ recipe/ fmt:link" />
I can see why you tested the template, but should it have an independent rule?