Summary
This issue tracks ongoing and future work to improve Onyx, following the completion and review of the original audit work.
While the audit focused on performance and scalability, current efforts are shifting toward simplifying Onyx internals. Over time, incremental optimizations and feature additions have increased internal complexity, making changes harder to reason about, test, and evolve safely. Addressing this complexity is necessary to improve correctness and maintainability, and to enable future performance work without introducing additional risk.
This issue replaces the original audit issue as the primary coordination point for Onyx improvements.
As a start point we will be focusing on the simplification of useOnyx API, namely the initWithStoredValues, allowStaleData, canBeMissing and allowDynamicKey options.
Additionally, we already have some efforts in Onyx internals to simplificate and improve its performance:
Issue Owner
Current Issue Owner: @fabioh8010
Summary
This issue tracks ongoing and future work to improve Onyx, following the completion and review of the original audit work.
While the audit focused on performance and scalability, current efforts are shifting toward simplifying Onyx internals. Over time, incremental optimizations and feature additions have increased internal complexity, making changes harder to reason about, test, and evolve safely. Addressing this complexity is necessary to improve correctness and maintainability, and to enable future performance work without introducing additional risk.
This issue replaces the original audit issue as the primary coordination point for Onyx improvements.
As a start point we will be focusing on the simplification of
useOnyxAPI, namely theinitWithStoredValues,allowStaleData,canBeMissingandallowDynamicKeyoptions.Additionally, we already have some efforts in Onyx internals to simplificate and improve its performance:
Issue Owner
Current Issue Owner: @fabioh8010