-edit-
Adding details to the issue as this was previously discussed with harry in DM.
When debugging a contract with storage, the debugger will show a list of random numbers (these are 32-bit hashes of the storage key). See the first 15 seconds of this video where Harry explains it; https://youtu.be/HSYeXzUp65A?feature=shared&t=137
This issue is about reverting those key hash changes and turning it back into a "raw storage" view. Imagine you have a contract with 20 storage records. Then it is a real pain to find which random number in that list matches your storage key. Instead the list should be based on the Key value. Apparently it is part of the storage schema changes that are in the develop branch.
To quote what Harry said
I should be able to bring that over to the main branch w/o the rest of the storage schema work
-edit-
Adding details to the issue as this was previously discussed with harry in DM.
When debugging a contract with storage, the debugger will show a list of random numbers (these are 32-bit hashes of the storage key). See the first 15 seconds of this video where Harry explains it; https://youtu.be/HSYeXzUp65A?feature=shared&t=137
This issue is about reverting those key hash changes and turning it back into a "raw storage" view. Imagine you have a contract with 20 storage records. Then it is a real pain to find which random number in that list matches your storage key. Instead the list should be based on the Key value. Apparently it is part of the storage schema changes that are in the develop branch.
To quote what Harry said