Failing test for ancestry #418
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Lol! Blast from the past :) I think the best first step would be a failing test case that doesn't require another gem. I'd assume it should be possible to simulate the failing scenario without |
|
heh, I know hey. We're having problems with this and I found this open issue so thought I'd try lend a hand. Will take a swing at removing the ancestry dependency for the test. |
|
Closing this for now @wooly. If you want to pursue it again let me know. Also try out: https://github.com/brendon/positioning I've not used |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@brendon first attempt at a failing test for #131