Account storage inspection about flow-emulator

[sideninja]

I am dreaming a bit but also playground backend using FlowKit would be also be a killer feature.

Oh, believe we are both dreaming about this ;) actually, I'm already doing some planning on how we could refactor the playground and use flowkit instead, actually not just playground but also vscode extension and just offer that functionality as part of the LS for all the IDEs to use. Super early phase tho, so more planning will be needed but in my mind these are first steps we need to take to get there one day.

[sideninja]

The PR is almost ready, the implementation works, I need to think about FVM values now and further test it.

[bluesign]

This is really great idea, though I am in favor on solving on cadence side ( due to internal changes on storage happening all the time )

I think we have all the parts we need ( though they may be not made it to secure cadence due to non-technical reasons :tinfoilhat: )

• Here we have AuthAccount for scripts PR: onflow/cadence#1240
• I think this is also very short PR: onflow/cadence#208

when we have this both, we will have this functionality with plus nothing to maintain when something internal changes.

[sideninja]

I agree 💯 that this will and should be solved by Cadence but it may take some time to get there, so an abstraction of this functionality in the emulator won't hurt, after Cadence adds this we will just make sure to deprecate the API. This is needed by above-mentioned tools in the short term.

[bluesign]

Ah then I agree totally with this time frame. Also integration with FlowKit would be super nice.

I am dreaming a bit but also playground backend using FlowKit would be also be a killer feature.