Elsewhere in the GQL api we use a scalar value to represent the block height, however in the gql extension that provides the block number of each request it uses a plain js number. We should aim to use the same types for representing block height where possible within the GQL api.
example response:
{
"data": {
"blocks": {
"edges": [
{
"node": {
"header": {
"height": "42531359"
}
}
}
]
}
},
"extensions": {
"current_consensus_parameters_version": 7,
"current_fuel_block_height": 42531359,
"current_stf_version": 32
}
}
Elsewhere in the GQL api we use a scalar value to represent the block height, however in the gql extension that provides the block number of each request it uses a plain js number. We should aim to use the same types for representing block height where possible within the GQL api.
example response:
{ "data": { "blocks": { "edges": [ { "node": { "header": { "height": "42531359" } } } ] } }, "extensions": { "current_consensus_parameters_version": 7, "current_fuel_block_height": 42531359, "current_stf_version": 32 } }