Greg

I would update the existing generate method.

Let's define the whole interface here. Also make sure to link in the language server that will be affected and ping some of known users of flowkit like @bjartek

I would change `Create` -> `CreateAccount` Is this needed? `prepareTransaction`, if it's not exported then it probably shouldn't be part of it. I think I would make sense to name...

Yep, it's part of the list in the issue. Context should be the first arg for all of the methods. I would even think about not exposing all the methods...

Config as in accessing the state? That should already be possible, although not exposed by the proposed interface, but that might be fine. I don't want to only have one...

Honestly, I think an important part of the flowkit is flow.json. I see the flow.json to be the glue between different flow tools and having a library that knows how...

> One thing I'm not too sure how to do is how to change the return values per each function for different test cases You can use a service like...

If I understand the problem correctly, it might be a good idea to include this as part of the Cadence linting process. Anyway we make transaction code look more concise...

@bjartek any updates on this?

@bjartek sorry I was just removing myself as an assignee from tasks that are not in progress since they might be redistributed to others. For this task, I actually thought...