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

Improved API when performing queries, removing or similar operations on frozen older version of an entity #1723

Open
rorbech opened this issue Apr 16, 2024 · 1 comment

Comments

@rorbech
Copy link
Contributor

rorbech commented Apr 16, 2024

Problem

There are a number of cases where it operations require the inputs to be of the most recent version for core to actually match the right entities. Specifically seen in #1712, but there are also similar API call sites where we could improve #1660.

Solution

We should find a way to improve these APIs by either:

  • Improve the type system so that it is just not that easy to end up calling with outdated/frozen objects
  • Throwing when invoked with outdated objects
  • Automatically resolve old objects in the updated context

Alternatives

No response

How important is this improvement for you?

I would like to have it but have a workaround

Feature would mainly be used with

Local Database only

Copy link

sync-by-unito bot commented Apr 16, 2024

➤ PM Bot commented:

Jira ticket: RKOTLIN-1069

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

1 participant