@22516c1b4e5d40db919e5e56a040c5670eac947fcb53a71207d5ce640a973820 [Posted on DevHub](/devgovgigs.near/widget/Post?id=3280) ## Solution: IterableMap-related `store` collections test coverage. ###### Requested amount: 5000 USDT ###### Requested sponsor: @neardevdao.near # Overview The goal of this proposal is to enhance the [IterableMap](https://github.com/near/near-sdk-rs/pull/1164) implementation by covering all the `store` collections it uses under the hood with tests. That's takes us a step closer to deprecating some of the `store` and `collections` collections. # Background [IterableMap](https://github.com/near/near-sdk-rs/pull/1164) aims at replacing `store::UnorderedMap` collection as well as `collections::UnorderedMap`. The former has issues with iteration based on `remove/insert` ratio. The relevant issue can be found [here](https://github.com/near/near-sdk-rs/issues/1134). The latter should have been deprecated a while ago due to the nuances related to flushing updates to underlying storage, more info can be found [here](https://github.com/near/near-sdk-rs/issues/1134#issuecomment-1939635957). # Deliverables 1. Covering `store::IndexMap`, `store::Vector`, `utils::StableMap` and `store::LookupMap` with more tests, fixing potential issues. 2. Making sure that all of these collections have been properly documented. # Timeline and funding The estimated timeline for delivery is within the next month, with a total funding requirement of 5000 USDT, paid once the PR is raised and ready for review.