- BREAKING: We've made some significant (~4x) performance improvements to the cache and eliminated all our known Thread Sanitizer issues by removing some overly agressive multithreading and our internal Promises implementation. (#1531) Related Changes:
- POSSIBLY BREAKING: These improvements caused changes in our
NormalizedCache
andApolloClientProtocol
protocols, so if you're implementing these yourself, you'll need to update. - BREAKING: Removed the
loadRecords(forKeys:)
method onReadTransaction
. We'd recommended that you use eitherread
orreadObject
with the transaction, but if you were usingloadRecords
, you will need to shift to those other methds. - NEW:
ApolloStore
'sload(query:resultHandler:)
method now also takes an optional callback queue.
- POSSIBLY BREAKING: These improvements caused changes in our
- NEW: Added the ability to say whether the results from a mutation should be published to the store are not. This is a boolean value which defeaults to
true
, to match existing behavior. (#1521) - BREAKING: The setter for
Atomic
'svalue
is no longer public to prevent accidental misuse. If you were using this, use themutate
method instead to ensure the thread lock works properly. (#1538)