-
Notifications
You must be signed in to change notification settings - Fork 101
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
Field aliasing via delegated schema not remapping field names #164
Comments
Sorry for the delay in response @islishude Reopening, as it's a bug I need to investigate. The expectation is for the aliases to be remapped after the delegated response is returned from Hasura, since On a side-node, the specific alias you're making here should be addressed in #175 |
Hello, @islishude and @rhyslbw. It seems that this issue still persists for Here is a sample query to reproduce it. query (
$where: Epoch_bool_exp
){
epochs( where: $where ) {
protocolParams {
feeFixed: minFeeA
feePerByte: minFeeB
}
}
} Any query parameters will do, such as the following {
"where": {
"number": {
"_eq": 156
}
}
} The error message is the following. {
"errors": [
{
"message": "Cannot return null for non-nullable field ShelleyProtocolParams.minFeeA.",
"locations": [
{
"line": 4,
"column": 7
}
],
"path": [
"epochs",
0,
"protocolParams",
"feeFixed"
],
"extensions": {
"code": "INTERNAL_SERVER_ERROR",
"exception": {
"stacktrace": [
"Error: Cannot return null for non-nullable field ShelleyProtocolParams.minFeeA.",
" at completeValue (/app/node_modules/graphql/execution/execute.js:560:13)",
" at completeValueCatchingError (/app/node_modules/graphql/execution/execute.js:495:19)",
" at resolveField (/app/node_modules/graphql/execution/execute.js:435:10)",
" at executeFields (/app/node_modules/graphql/execution/execute.js:275:18)",
" at collectAndExecuteSubfields (/app/node_modules/graphql/execution/execute.js:713:10)",
" at completeObjectValue (/app/node_modules/graphql/execution/execute.js:703:10)",
" at completeValue (/app/node_modules/graphql/execution/execute.js:591:12)",
" at completeValueCatchingError (/app/node_modules/graphql/execution/execute.js:495:19)",
" at resolveField (/app/node_modules/graphql/execution/execute.js:435:10)",
" at executeFields (/app/node_modules/graphql/execution/execute.js:275:18)"
]
}
}
}
],
"data": {
"epochs": [
{
"protocolParams": null
}
]
}
} |
This issue may be the culprit. ardatan/graphql-tools#3267 |
Sorry @dingxiangfei2009 , this shouldn't have been closed. We'll see if the library author has an ideas |
I will close this issue since it doesn't have any activities any more. IF YOU NEED IT, PLEASE FILE A NEW ONE. |
api: https://cardano-graphql-mainnet.daedalus-operations.com/
The text was updated successfully, but these errors were encountered: