-
-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix position when no serial positions #223
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
f5806e3
Fix position in case of not serial positioning in db
PoslinskiNet c674513
New specs
PoslinskiNet 4dca66d
Merge branch 'master' into fix-not-serial-positions
jpalumickas 2330682
Update tests
jpalumickas 2abb846
Use update_attributes instead of update
jpalumickas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,6 +43,32 @@ def test_next_prev | |
assert_nil ListMixin.where(id: 4).first.lower_item | ||
end | ||
|
||
def test_next_prev_not_regular_sequence | ||
ListMixin.all.each do |item| | ||
item.update_attributes(pos: item.pos * 5) | ||
end | ||
|
||
assert_equal [1, 2, 3, 4], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
|
||
ListMixin.where(id: 2).first.move_lower | ||
assert_equal [1, 3, 2, 4], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
|
||
ListMixin.where(id: 2).first.move_higher | ||
assert_equal [1, 2, 3, 4], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
|
||
ListMixin.where(id: 1).first.move_to_bottom | ||
assert_equal [2, 3, 4, 1], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
|
||
ListMixin.where(id: 1).first.move_to_top | ||
assert_equal [1, 2, 3, 4], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
|
||
ListMixin.where(id: 2).first.move_to_bottom | ||
assert_equal [1, 3, 4, 2], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
|
||
ListMixin.where(id: 4).first.move_to_top | ||
assert_equal [4, 1, 3, 2], ListMixin.where(parent_id: 5000).order('pos').map(&:id) | ||
end | ||
|
||
def test_next_prev_groups | ||
li1 = ListMixin.where(id: 1).first | ||
li2 = ListMixin.where(id: 2).first | ||
|
@@ -53,9 +79,9 @@ def test_next_prev_groups | |
assert_equal [li2, li3], li1.lower_items(2) | ||
assert_equal [], li4.lower_items | ||
|
||
assert_equal [li1, li2], li3.higher_items | ||
assert_equal [li2, li1], li3.higher_items | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it going to break existing code if the order of returned higher items is in reverse to what it used to be? |
||
assert_equal [li1], li2.higher_items | ||
assert_equal [li2, li3], li4.higher_items(2) | ||
assert_equal [li3, li2], li4.higher_items(2) | ||
assert_equal [], li1.higher_items | ||
end | ||
|
||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering with these methods. Do we need the branching here. Could the first branch not handle all situations (i.e. consecutive numbering and non-consecutive?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PoslinskiNet can you answer that ? 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is possible, but didn't want to change the default behaviour, just handle "non-consequence" branch, so consider that as a refactor :).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, yes that makes sense.