Do we still need FUEL_NETWORKL_URL? 🤔

[petertonysmith94]

Full context

@Torres-ssf FUEL_NETWORK_URL constant is mainly ( if not only ) used within our tests.

@danielbate The one caveat is that when copying from snippets, FUEL_NETWORK_URL used a ternary that could evaluate but live and local networks, so it could be extracted from snippets. Whereas someone now will need to change the constant dependent on if they are working on testnet or locally.

@arboleya I wonder if such a constant should be static and avoid the ternary.

What do we want to do about FUEL_NETWORK_URL?

[arboleya]

TL;DR of my proposal:

• DEVNET_NETWORK_URL
• TESTNET_NETWORK_URL
• NETWORK_URL — upcoming mainnet

I also don't think we need a LOCAL_NETWORK_URL because it's user-defined and, when combined with the fuels CLI and launch{Test}Node, the port is dynamic.

[petertonysmith94]

Will FUEL_NETWORK_URL also be made redundant by the launchTestNode integration?

How do we want to display the URL in the documentation? 🤔

[arboleya]

Yes, if you use launchTestNode, you should not need any constant.

I think could ditch FUEL_NETWORK_URL and keep only:

• DEVNET_NETWORK_URL
• TESTNET_NETWORK_URL
• NETWORK_URL — upcoming mainnet

[petertonysmith94]

Yes, if you use launchTestNode, you should not need any constant.

I think could ditch FUEL_NETWORK_URL and keep only:

• DEVNET_NETWORK_URL
• TESTNET_NETWORK_URL
• NETWORK_URL — upcoming mainnet

I tend to agree - created #2644 for this

[petertonysmith94]

Discussion concluded