Deniz Mert Edincik

On the access control page, add "Remember that if you can access a let dictionary or array you can mutate its contents, this includes when they are pub or access(all)...

I think the real risk here is accidentally sending some transactions with your main account instead of the local (project) account. This can mess up in an ugly way. I...

I agree with @joshuahannan in this case, but also I feel like we lost the war on msg.sender pattern with resource owner already. This will be more clear vs people...

@turbolent off-topic a bit, but seeing recently a lot of `forEach` and iterators around issues. Can't we implement something more generic on arrays ? Something like: generic iterators on lazy...

Do we want to support multiple emulators? I always though it is some kind of default setting place, more like: ``` "emulator": { "defaultPort": 3569, "defaultServiceAccount": "emulator-account2" } ``` Actually...

Oh this would be great addition, I was just about the open an issue. Context: I am trying to make dev-wallet to work with flow.json config, additional to FCL Wallet....

Here we can maybe add one layer of "network" on accounts like other sections, if it is missing, we can fix flow.json on first run. ( detecting with chainID )...

@sideninja I meant something like below: ( instead of `network` property on account ) ``` "accounts": { "emulator":{ "emulator-account": { "address": "f8d6e0586b0a20c7", "key": "5e9aaf23d1143642b7d9f2da8dd4a03930e1e5995581e04187e20bdbc6a4f22d" } }, "mainnet":{ .... } },...

We can infer from the address, but it would be one more step to handle to keep it up. I have something like this in my flow.json: ``` "networks": {...

> How do you see emulators creating those accounts? especially if the addresses don't reflect the order of the used address generator? I was thinking putting Accounts to `map[UInt64]Account` (where...