Skip to content

Store trait sequences as tuples, not lists#620

Merged
kylebarron merged 6 commits into
mainfrom
kyle/store-tuples-not-list
Sep 3, 2024
Merged

Store trait sequences as tuples, not lists#620
kylebarron merged 6 commits into
mainfrom
kyle/store-tuples-not-list

Conversation

@kylebarron

@kylebarron kylebarron commented Sep 3, 2024

Copy link
Copy Markdown
Member

Ref #592 (comment)

This should be easier to follow for users. Mutating a list trait doesn't propagate any updates to the frontend. Rather, you must set a new object. Storing tuple traits instead of list traits means that it's impossible for the user to accidentally not sync those updates to the frontend.

@kylebarron kylebarron changed the title Store sequences of traits as tuples, not lists Store trait sequences as tuples, not lists Sep 3, 2024
@kylebarron kylebarron enabled auto-merge (squash) September 3, 2024 16:47
@kylebarron kylebarron merged commit e67fb8a into main Sep 3, 2024
@kylebarron kylebarron deleted the kyle/store-tuples-not-list branch September 3, 2024 17:24
roger120981 pushed a commit to roger120981/lonboard that referenced this pull request Jul 14, 2025
Ref
developmentseed#592 (comment)

This should be easier to follow for users. Mutating a list trait doesn't
propagate any updates to the frontend. Rather, you must set a new
object. Storing tuple traits instead of list traits means that it's
impossible for the user to accidentally not sync those updates to the
frontend.
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.

1 participant