You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user does a call targeting a newer or older version of the provider (fuel-core), the SDK implementation can be ahead of behind the fuel-core version, making the SDK throw unexpected errors, making it difficult for the users to understand what is causing for the issue.
The proposal is to add a fuel-core version query before other queries or with all other queries. To get the version of the fuel-core and compare it with a config range version inside the SDK code. In this way, we can;
If the versions are not compatible, throw an error explicating talk about it;
If a transaction reverts, we can log in with the error and also the fuel-core version making it easier to receive/give support.
The text was updated successfully, but these errors were encountered:
When a user does a call targeting a newer or older version of the provider (fuel-core), the SDK implementation can be ahead of behind the fuel-core version, making the SDK throw unexpected errors, making it difficult for the users to understand what is causing for the issue.
The proposal is to add a fuel-core version query before other queries or with all other queries. To get the version of the fuel-core and compare it with a config range version inside the SDK code. In this way, we can;
The text was updated successfully, but these errors were encountered: