TS SDK pain points

[matt-user]

Hey all, I finished working on a frontend using the ts-sdk and thought I would share some pain points.

1. Command fuels versions not working #1882
2. Nit: fuels dev docs should mention build, type gen, and deploy (I think it only mentions build and deploy)
3. when I used fuels init without create fuels I had difficulty using fuels dev "default account cannot deploy contracts bc of insufficient funds"
4. I didn't use create fuels bc I didn't see it in the cli portion of the docs
5. I also had issues with the private key field not working on the fuels config.
6. Typegen does not automatically use configured inputs and outputs specified in the config
7. Difficulty importing enum from contract Abi so I had to remember what the underlying data of the enum
8. Its hard to distinguish log events from each other. I have to look at the sway code.
9. Add some documentation about the .fuels folder generated (just a note that it gets created from fuels is probably sufficient)
10. Command fuels dev hangs on generating types #1886
    
11. It would also be nice to just have to list one connector and not all of them

[arboleya]

@matt-user Thanks for putting this feedback together.

I did some formatting and started addressing the first point.

[arboleya]

@matt-user How often the 10th item happens?

[matt-user]

It happened every time for me. I was not able to get it to work.

[danielbate]

Difficulty importing enum from contract Abi so I had to remember what the underlying data of the enum

Do you have an example for this? We can definitely improve enums, #1844 suggests something similar so may be able to sync up the solution.

[matt-user]

Looking back my issue was actually importing the enums not constructing them. I'd like to do something like this gameState === StateOutput.Ended, but I can't import StateOutput so instead I have to do gameState === "Ended". It could be an issue in how I build my app I guess