Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

coordinating reducer version upgrades #22

Open
carlsverre opened this issue Sep 11, 2023 · 0 comments
Open

coordinating reducer version upgrades #22

carlsverre opened this issue Sep 11, 2023 · 0 comments
Assignees
@carlsverre
Labels
reducer

Comments

@carlsverre
Copy link
Contributor

carlsverre commented Sep 11, 2023 •
edited
Loading

Upgrading a reducer requires careful coordination between the server and the client.

Need to look at this from the perspective of client-server reducer version mismatch. When this occurs, the server is in a unique position to coordinate the upgrade.

The other problem is when the client submits mutations that were created by an older reducer version. This may require extending the reducer API to support "mutation migration" or lensing.
@carlsverre carlsverre converted this from a draft issue Sep 11, 2023
@carlsverre carlsverre changed the title reducer upgrade coordinating reducer version upgrades Sep 11, 2023
@carlsverre carlsverre self-assigned this Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carlsverre carlsverre

Labels
reducer
Projects
No open projects
sqlsync roadmap
Status: Planning
Milestone
No milestone
Development

No branches or pull requests
1 participant
@carlsverre