-
Notifications
You must be signed in to change notification settings - Fork 9
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
chore: Upgrade apollo packages to prepare for gateway refactor #128
chore: Upgrade apollo packages to prepare for gateway refactor #128
Conversation
…submitted field inside the call instruments query
}); | ||
import { GraphQLScalarType, Kind } from 'graphql'; | ||
|
||
export type AnswerType = number | string | Date | boolean | number[] | unknown; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is unknown needed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is needed after update of graphql. Most probably they changed the types and here is the result https://github.com/graphql/graphql-js/blob/main/src/type/definition.ts#L545. It is a bit disappointing because now the AnswerType is considered as unknown and the other types doesn't make much sense anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides removing commented code looks fine.
Description
This PR is updating all the apollo packages to latest and moves the backend one step closer to upgrading gateway to version 2.
Motivation and Context
We were using quite old apollo packages and it is good to be up to date and improve functionality around it.
How Has This Been Tested
Fixes
https://jira.esss.lu.se/browse/SWAP-2770
Changes
Changes are mainly fixes after updating apollo packages