Skip to content

Comments

Handle non-numeric order in _ct_after_save#486

Open
sampatbadhe wants to merge 1 commit intoClosureTree:masterfrom
sampatbadhe:fix/non-numeric-order-column-reordering
Open

Handle non-numeric order in _ct_after_save#486
sampatbadhe wants to merge 1 commit intoClosureTree:masterfrom
sampatbadhe:fix/non-numeric-order-column-reordering

Conversation

@sampatbadhe
Copy link
Contributor

Summary

Handle non-numeric order in _ct_after_save

Only run reorder/scope-change logic when the order column is numeric. The _ct_after_save flow was restructured to guard calls to _ct.scope_changed? and sibling reordering with _ct.order_is_numeric?, preventing errors when models use a non-numeric order column.

Fixes undefined method `_ct_reorder_siblings' for an instance of Tag

Only run reorder/scope-change logic when the order column is numeric. The _ct_after_save flow was restructured to guard calls to _ct.scope_changed? and sibling reordering with _ct.order_is_numeric?, preventing errors when models use a non-numeric order column.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

undefined method `_ct_reorder_siblings' for an instance of Tag

1 participant