Skip to content
This repository has been archived by the owner on Apr 13, 2021. It is now read-only.

After state in changes middleware should be optimized #7

Open
carsonfarmer opened this issue Sep 18, 2020 · 0 comments
Open

After state in changes middleware should be optimized #7

carsonfarmer opened this issue Sep 18, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@carsonfarmer
Copy link
Member

There are some suggestions in comments that should be explored. For example, we could just use undefined[] for deletes, and req.values for add/put if not we aren't waiting for auto-incrementing indexes to come back from IndexedDB (which, maybe we don't need to worry about because we're always using ulids?). If that is the case, then we can just always compute the :after: state using jsonpatch.applyPatch, or we could even just lazily compute the after state when we actually need them?

@carsonfarmer carsonfarmer added the enhancement New feature or request label Sep 18, 2020
@carsonfarmer carsonfarmer self-assigned this Sep 18, 2020
@carsonfarmer carsonfarmer added this to To do in Threads via automation Sep 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Threads
  
To do
Development

No branches or pull requests

1 participant