local storage wrapper for both react-native and browser. Support size controlling, auto expiring, remote data auto syncing and getting batch data in one query.
MIT License
3.02k
stars
268
forks
source link
Incomplete Cleanup of Key_ID Entries in _m After removeItem #272
There seems to be an issue with the removeItem function in our storage system, specifically with entries formatted as key_id. After invoking removeItem, some of these entries are not fully cleaned up and remain in the _m mapping object. This residual data could potentially cause unexpected behavior or errors in subsequent operations.
Steps to Reproduce
Insert multiple items using keys formatted as key_id (e.g., loginInfo_shortToken).
Remove these items using removeItem.
Check the _m object for any residual entries.
Expected Behavior
All entries related to the specified key_id should be completely removed from _m after the execution of removeItem.
Actual Behavior
Some entries remain in _m even after their supposed deletion, leading to unnecessary bloat and potential inconsistencies.
Possible Impact
Inefficiencies due to bloated memory usage.
Potential for retrieving outdated or incorrect data.
General instability in storage operations.
Suggested Actions
Review and revise the cleanup logic in removeItem to ensure all references are effectively removed.
Implement additional checks and balances to verify the integrity of _m after deletion operations.
This issue needs attention to prevent possible data integrity problems and to maintain optimal performance of the storage system.
Description
There seems to be an issue with the
removeItem
function in our storage system, specifically with entries formatted askey_id
. After invokingremoveItem
, some of these entries are not fully cleaned up and remain in the_m
mapping object. This residual data could potentially cause unexpected behavior or errors in subsequent operations.Steps to Reproduce
key_id
(e.g.,loginInfo_shortToken
).removeItem
._m
object for any residual entries.Expected Behavior
All entries related to the specified
key_id
should be completely removed from_m
after the execution ofremoveItem
.Actual Behavior
Some entries remain in
_m
even after their supposed deletion, leading to unnecessary bloat and potential inconsistencies.Possible Impact
Suggested Actions
removeItem
to ensure all references are effectively removed._m
after deletion operations.This issue needs attention to prevent possible data integrity problems and to maintain optimal performance of the storage system.
Thank you!