dm-is-nested set - fix to current spec failures
Reported by glenndavy | October 21st, 2008 @ 01:35 AM
hi a small change to is nested set to get tests to pass. when an unviable move of node is requested (say move(:higher) when already at highest position) then false should be returned according to spec. The result is masked in the move method by 'save' on last line, so this patch only saves if move(:token) returns non false.
glenn
Comments and changes to this ticket
-
glenndavy October 21st, 2008 @ 04:48 AM
- no changes were found...
-
Dan Kubb (dkubb) December 2nd, 2008 @ 04:58 AM
- Assigned user cleared.
- State changed from “new” to “hold”
Glen, can you confirm this is still a problem for you with the latest in dm-more?
-
Dan Kubb (dkubb) December 4th, 2008 @ 03:16 AM
- State changed from “hold” to “resolved”
I've actually confirmed that the code in dm-is-nested set has been updated with a similar patch prior to the last gem release. Marking this ticket as resolved.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
- Nobody is watching this ticket.