Deniz Mert Edincik

`access` is better choice and much cleaner. For the magic part, I meant something like this: ( it was for a smarter way to detect protocol from host, instead of...

also we can keep `host` and detect if it is url with schema ( then use the schema as protocol ) if not we default to GRPC. deprecation seems a...

I think iteration is nice for sure, but also additionally some kind of `query` functionality can be useful. ( to limit search area and return array of struct ) If...

I think best option is to expose storageManager ( or whatever we call it ) to both PublicAccount and AuthAccount. ( Immutability can work here very good ) > It...

@turbolent wouldn't it possible to handle this on cadence side ? Eventually it will be just a dictionary, {String : [Path]} where key is a type identifier. I don't think...

@turbolent this is very good question actually. In the context of containers, multi level storage, I see those options: - array / dictionary - composite resource For composite resources, I...

I think solution here is detecting mutation ( not avoiding ). Technically nothing can iterate on mutating object. So mutation should just invalidate the cursor. I don't know much about...

@SupunS good idea, maybe we can do something like: With built in enum: ``` enum StorageDomain{ ANY PUBLIC PRIVATE STORAGE } ``` and in AuthAccount: ``` pub fun getPaths(_ StorageDomain):...

> I think the commands to deploy contracts manually and not through flow project should just be removed, it is just confusing to have multiple ways to do it. Last...

Also maybe we can add support to OS keyrings with https://github.com/99designs/keyring or https://github.com/zalando/go-keyring.