Thanks. I found that ticket after posting but thought it was more related
to passing a non-existent transition. Here's the workaround I'm using in
case anyone stumbles across this thread:
<%
transition = this.lifecycle.find_transition("complete", current_user)
if transition
%>
<transition-button transition="complete" if="&this.state=='reviewing'"
label="Accept"/>
<%
end
%>
Obviously if you are planning on using this for more than one button it
would be wise to refactor into a tag and pass a param for the transition
name/label.
On Fri, May 28, 2010 at 4:40 PM, Matt Jones <[email protected]> wrote:
> On Fri, May 28, 2010 at 11:37 AM, Chris Apolzon <[email protected]> wrote:
> > I jumped into the Hobo codebase again and found that when rendering the
> > transition button, it loops over the available_transitions and verifies
> each
> > with can_run?. It eventually breaks when it calls guard_ok? as the if
> fails
> > at this point. In an ideal world should I be checking this myself before
> > trying to put a transition-button on the page? Or is this an oversight
> by
> > hobo?
>
> It's a bug:
>
> https://hobo.lighthouseapp.com/projects/8324/tickets/620
>
> --Matt Jones
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hobo Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<hobousers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/hobousers?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
