-
Notifications
You must be signed in to change notification settings - Fork 25
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
Feat/cleanup #913
base: feature/federated_search
Are you sure you want to change the base?
Feat/cleanup #913
Conversation
…s.total is not queried
@@ -26,7 +59,7 @@ export default ({ type, getServerSideFilter }) => { | |||
nestedFieldNames, | |||
filters: compileFilter({ | |||
clientSideFilter: resolvedFilter, | |||
serverSideFilter: getServerSideFilter(context), | |||
serverSideFilter: getServerSideFilter(), |
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.
this doesn't appear to be needed? As far as I read, es client is only thing in context and the filter ops shouldn't be used directly in that. thoughts? - Jon, Justin @
e26d4a1
to
7828313
Compare
tighten config resolver tighten config resolver
7828313
to
0a61fb1
Compare
simplify network supported type lookup
setup, cleanup field querying setup, cleanup field querying
e354ba1
to
074b775
Compare
fix resp
7740fd2
to
edafe93
Compare
import { Client } from '@elastic/elasticsearch'; | ||
import { GraphQLResolveInfo } from 'graphql'; | ||
|
||
export type Context = { | ||
esClient: Client; | ||
}; | ||
|
||
export type ResolverOutput<T> = T | Promise<T>; | ||
|
||
/** | ||
* GQL resolver | ||
* | ||
* @param root The parent object of a query. | ||
* @param args The query arguments. | ||
* @param context The context passed to apollo-server for queries. | ||
* @param info The GraphQL info object. | ||
* @return Returns resolved value; | ||
*/ | ||
export type Resolver<Root = {}, QueryArgs = Object, ReturnValue = undefined> = ( | ||
root: Root, | ||
args: QueryArgs, | ||
context: Context, | ||
info: GraphQLResolveInfo, | ||
) => ResolverOutput<ReturnValue> | ResolverOutput<ReturnValue>; |
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.
Add reusable GQL resolver type
createConnectionResolvers
as a top level TS file so everything below can be typedutils
folder dump, created distinct files__typename
distinction in network connected aggregations type, uses singular Aggregation type throughout