Skip to content

Implement renumeration of ordered tags upon collision - #5759

Merged
ara4n merged 2 commits into
developfrom
luke/renumerate-broken-ordered-sublists
Dec 4, 2017
Merged

Implement renumeration of ordered tags upon collision#5759
ara4n merged 2 commits into
developfrom
luke/renumerate-broken-ordered-sublists

Conversation

@lukebarnard1

@lukebarnard1 lukebarnard1 commented Dec 1, 2017

Copy link
Copy Markdown
Contributor

I was being bitten by this enough for me to want to fix it. This implementation really ought to be improved such that it doesn't tend towards being broken the more it is used.

I'm not convinced we should be trusting that the client has the correct state in it (and is therefore in a position to calculate a new order). If a different implementation didn't rely on the client having the correct client state, then let's do that.

One example would be to do a linked list where the tag on the room refers to the previously tagged room. This however has the potential for error if the client removes an item and then fails to reinsert it. This is probably a better weirdness than what we have currently, though.

I was being bitten by this enough for me to want to fix it. This implementation really ought to be improved such that it doesnt tend towards being broken the more it is used.
@dbkr dbkr assigned ara4n and unassigned dbkr Dec 4, 2017
@dbkr

dbkr commented Dec 4, 2017

Copy link
Copy Markdown
Member

@ara4n this is probably one for you

@ara4n

ara4n commented Dec 4, 2017

Copy link
Copy Markdown
Member

lgtm! embarrassing how easy the end soln was :S

@ara4n
ara4n merged commit 9835e2e into develop Dec 4, 2017
@t3chguy
t3chguy deleted the luke/renumerate-broken-ordered-sublists branch May 12, 2022 09:01
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.

3 participants