Magic IndexedDB v2.0.0-alpha9
NuGet: Magic.IndexedDb v2.0.0-alpha9
Core Fixes
Significant repair and alterations to .Cursor
. Alterations to the interface of what's allowed has occurred and significant bug fixes. Ordering has been better replicated as well to have the meta data driven ordering for Take
, Skip
, TakeLast
to better replicate indexedDB ordering in memory. This includes the cursor replicating situations where the predicate in the Where
now identifies indexed columns and orders by the indexed columsns, then by the inserted row ordering. As this replicates indexed query logic which is what the cursor engine is meant to do. As the purpose is that indexed versus cursor queries should have the same syntax and intent to simplify use.
Significant boosts to reliability should have occurred this update. Unit tests have been refactored to test many automated pathways. Tests went from ~90 unit tests to now 357 unit tests to validate a significant number of paths and syntax use.
The interfaces have been limited further, but for good reason to better replicate what's actually possible. Otherwise returned results are not able to process intent as it should. From here, once more stability is brought, the .Cursor
can be upgraded to grow in power instead of reeling it back.
There was a lot of oversight in unit testing recently due to browser caching claiming everything was wiped when that was not actually true. This created perceived reliability when it was failing in reality after specific updates. Unit tests are being beefed up to better catch pathway errors and prevent caching issues during testing.
Final Thoughts
If you notice any issues with bad path syntax that breaks or ordering, please leave an issue ticket!