Closed discorick closed 8 years ago
This explains the behavior: https://github.com/huboard/huboard-web/blob/master/ember-app/app/mixins/cards/card-move.js#L21
I created all these issues from the task-view, for some reason they were all assigned the exact same milestone_order
key values.
I'm unclear why this would cause the card to disappear, vs simply failing to reorder (or having nondeterministic order among the three with identical milestone_order
values).
So, to keep glimmer from loosing track of cards in the DOM sortable list - we are actually pulling the issue object out of a computed array. You can see here https://github.com/huboard/huboard-web/blob/master/ember-app/app/components/columns/hb-column.js#L14
It seems in this case (maybe because there is no change to the underlying data) the computed list is not rebuilding, which means the card is never placed back into the DOM.
Ran into a case where a care disappears on every move, then reappears when a render is forced on on the milestones view:
The card below meta-data (test-issue#7)
The card above meta-data (test-issue#6)
The meta-data of the card being moved: