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.

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

Align the management of the state of transient and persisted representations #3305

Open
sbegaudeau opened this issue Mar 30, 2024 · 0 comments

Comments

@sbegaudeau
Copy link
Member

sbegaudeau commented Mar 30, 2024

Once #3304 is done, we should be able to remove some of the differences in the way the state of a representation is managed between transient and persisted representation. Technically, the only different between the two should be:

  • How to retrieve the initial state (computed on the fly vs retrieved from the database)
  • What to do when a new state is computed (nothing vs persist it in the database)

By aligning the way the state is managed, we should be able to reduce the custom code that should be written for each representation, lower the risk for potential errors such as double saving and offer a uniform way to access the state of a representation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants