Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TS SDK feedback from the Fuel Istanbul Hacker House #1446

Closed
Dhaiwat10 opened this issue Nov 23, 2023 · 3 comments
Closed

TS SDK feedback from the Fuel Istanbul Hacker House #1446

Dhaiwat10 opened this issue Nov 23, 2023 · 3 comments

Comments

@Dhaiwat10
Copy link
Member

Dhaiwat10 commented Nov 23, 2023

  1. A ethers to fuels migration or comparison guide would be nice. Most of the hackers in the hacker house were new to Fuel but had some previous experience with ethers or other Ethereum tooling.
  2. I met some hackers who said that it would be easier for them to build React frontends with our SDK if we had dedicated React hooks. Something like wagmi. Someone from the Fuel community already started this project - fuels-react but it is no longer maintained.
  3. The docs for the wallet sdk and the ts sdk are not in the same place. This can be a bit tricky for new devs.
  4. We should have something like Rainbowkit for Fuel. Another React tooling request that is related to an Ethereum ecosystem counterpart. The frontend team has already built something like this but, again, it's not as easy to use as Rainbowkit. This is something we should look at.
  5. Our official dev quickstart on the new Fuel Docs Hub should utilize our new Fuels CLI and the scaffolding tool. Running typegen and build commands again and again is not needed anymore, and not a pleasant dev experience.
  6. There are not enough (or any) written guides or video guides where we (or someone else from the community) showcases how to build an app start-to-finish using the SDK.
  7. You need to have some balance in your wallet even if you want to just read from a contract (.simulate()). This is not ideal
@luizstacio
Copy link
Member

Hey, this is nice feedback. I'm going to comment on some of them here:
2. We already have an implementation of the hooks for interacting with the SDK and Wallet SDK. @fuel-wallet/react you can take a look at the docs: https://docs.fuel.network/docs/wallet/dev/hooks-reference/ is getting better on the new version that is going to be released with the new Connectors.
3. This is a on going conversation. And with the new version of the Wallet SDK, we can move it to TS-SDK.
4. We recently implemented a new Connectors interface inside the Wallet SDK to create multiple connectors FuelLabs/fuels-wallet#972. We are using the first version of it inside the https://alpha.fuel.network/bridge. This UI is provided by the package @fuel-wallet/react.
7. Not on the things we already solve, but it can be done using the fundWithFakeUTXO used by the getTransactionCost. We could add something similar on the dryRun method.

@nedsalk
Copy link
Contributor

nedsalk commented Nov 24, 2023

Related to point 1, there is already a similar issue #449. Mentioning it here for linking purposes.

@arboleya
Copy link
Member

arboleya commented Dec 7, 2023

@Dhaiwat10 Could you please create individual tasks? (just like I said here)

@FuelLabs FuelLabs locked and limited conversation to collaborators Dec 8, 2023
@arboleya arboleya converted this issue into discussion #1492 Dec 8, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants