Make intercepting interactions independent from saving (async)
lukasz-gryzbon opened this issue · comments
To minimise the library's impact on the application's performance, it would be beneficial to decouple the intercepting from the persisting, possibly at the cost of a slightly bigger memory footprint.
Requirements:
- interceptors should return to the main thread as quickly as possible
- persisting the interactions should be done asynchronously
- the size of the storage for intercepted interaction should be bounded
- in case the storage is at capacity, the intercepting should not be affected (non-blocking)
🎉 This issue has been resolved in version 1.2.10 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀