-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Replace fuel_core_client::client::types::ConsensusParameters
with fuel_tx::ConsensusParameters
#1312
Comments
I am able to remove the client type However, I'm not finding an existing Maybe if you can provide some more concrete context as to what you need to achieve, I can look in that direction. Or if I'm just misunderstanding anything, please let me know! |
Related: - #1312 Removes the `types::ConsensusParameters` type designed to duplicate the existing `fuel_tx::ConsensusParameters` type. Instead, `ChainInfo` can use the `fuel_tx` type directly. --------- Co-authored-by: Green Baneling <[email protected]>
Fixed by #1314 |
Related: - FuelLabs/fuel-core#1312 Removes the `types::ConsensusParameters` type designed to duplicate the existing `fuel_tx::ConsensusParameters` type. Instead, `ChainInfo` can use the `fuel_tx` type directly. --------- Co-authored-by: Green Baneling <[email protected]>
Related: - FuelLabs/fuel-core#1312 Removes the `types::ConsensusParameters` type designed to duplicate the existing `fuel_tx::ConsensusParameters` type. Instead, `ChainInfo` can use the `fuel_tx` type directly. --------- Co-authored-by: Green Baneling <[email protected]>
Currently there are three definitions of this type:
Some of the types are missing
from
anddefault
impls, which makes it inconvenient to work with for unit testing in forc.There is a way to go from client -> fuel-tx here
And a way from schema -> client here
But missing fuel-tx -> client
Brandon K:
We should be able to just replace
fuel_core_client::client::types::ConsensusParameters
withfuel_core_types::fuel_tx::ConsensusParameters
Similarly, for
NodeInfo
The text was updated successfully, but these errors were encountered: