Skip to content
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

Include all supported connectors in the create fuels template #2677

Open
Dhaiwat10 opened this issue Jul 1, 2024 · 1 comment · May be fixed by #2691
Open

Include all supported connectors in the create fuels template #2677

Dhaiwat10 opened this issue Jul 1, 2024 · 1 comment · May be fixed by #2691
Assignees
Labels
chore Issue is a chore p2 Low Priority
Milestone

Comments

@Dhaiwat10
Copy link
Member

Right now the create fuels template only includes one connector - the Fuel Wallet. We should include all the supported ones: https://github.com/FuelLabs/fuel-connectors/tree/main/packages

@Dhaiwat10 Dhaiwat10 added the chore Issue is a chore label Jul 1, 2024
@Dhaiwat10 Dhaiwat10 added this to the 0.x mainnet milestone Jul 1, 2024
@petertonysmith94
Copy link
Contributor

We're currently using the defaultConnectors from v0.5.0, which is the latest release for @fuels/connectors on NPM.

connectors: defaultConnectors({
devMode: ENABLE_FUEL_DEV_CONNECTOR,
}),

v0.5.0 only has the following default connectors:

FuelWalletConnector
FueletWalletConnector
BurnerWalletConnector

Later versions (v0.8.1) has the following default connectors:

FuelWalletConnector
BakoSafeConnector
FueletWalletConnector
WalletConnectConnector
BurnerWalletConnector

I've asked the question whether the latest release is out of date and whether this should be on v0.8.1 :)

@arboleya arboleya added p1 Medium priority p2 Low Priority and removed p1 Medium priority labels Jul 2, 2024
@Dhaiwat10 Dhaiwat10 self-assigned this Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Issue is a chore p2 Low Priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants