Improved API when performing queries, removing or similar operations on frozen older version of an entity
rorbech opened this issue · comments
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
➤ PM Bot commented:
Jira ticket: RKOTLIN-1069