I'm submitting a...Bug report
[ ] Regression
[*] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
Hello,
I'm using the graphql example( in the example directory of nest) with the Cat CRUD and i try to use a union type and interface but i didn't find a way to do it.
When i try to request my data with a fragment, i have the following error :
"Abstract type MutationResult must resolve to an Object type at runtime for field Mutation.createCat with value "[object Object]", received "undefined". Either the MutationResult type should provide a "resolveType" function or each possible types should provide an "isTypeOf" function."
There is nothing in the doc explaining how to use union / interface, and there is nothing in the graphql example.
In the apollo documentation, the type resolver ( here "Cat" Resolver") should implement a __resolveType function. I tried to set this function in the @resolver('Cat') class CatsResolvers
but it's not working.
I tried to add it on the cat resolvers class
Expected behavior
The request should return either a Cat item or GraphQLErrorItem from my schema definition.
Minimal reproduction of the problem with instructions
export interface GraphQLError {
readonly message: string;
readonly errorCode: number;
readonly type: string;
}
type GraphQLError {
message: String
errorCode: Int
type: String
}
union MutationResult = Cat | GraphQLError
- change the createCat Mutation in the schema
- createCat(name: String, age: Int): MutationResult
- add the function in cats.resolvers.ts in the CatsResolvers class
__resolveType(obj, context, info): string{
return obj.errorCode ? 'GraphQLError' : 'Cat';
}
What is the motivation / use case for changing the behavior?
Environment
Nest version: 4.5.10 (core)
For Tooling issues:
- Node version: 9.4
- Platform: Mac
Others:
@nestjs/graphql v5.0.0 not published?
When I run the nest sample 12-graphql-apollo
, it throws some errors
TSError: ⨯ Unable to compile TypeScript:
src/app.module.ts(8,19): error TS2339: Property 'forRoot' does not exist on type 'typeof GraphQLModule'.
Hi,
I have an issue, when merge types and create schema, on terminal console show errors like this:
node:8726) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: buildASTSchema.getDescription is not a function
(node:8726) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled willterminate the Node.js process with a non-zero exit code.
this is my code
const typeDefs = this.graphQLFactory.mergeTypesByPaths('./**/*.graphql');
const schema = this.graphQLFactory.createSchema({ typeDefs });
consumer
.apply(graphqlExpress(req => ({ schema: {}, rootValue: req })))
.forRoutes({ path: '/graphql', method: RequestMethod.ALL });
It is possible to provide RXJS support for resolver functions (@Query()
, @Mutation()
, @ResolveProperty()
, ...) ? Like nest route handler, they could return RXJS observable streams :
@Query()
findAll(): Observable<any[]> {
return of([]);
}
I using fastify in nestjs as default, but i can not using this package. How should I do it?
Hallo,
in a previous release there has been the GraphQLFactory provider with the createSchema()-function. This has been removed and it seems there is no way to pass merged GraphQL types to GraphQLModule.forRoot(). Am I right or did I overlook something?
What is the reason to remove support for predefined types?
My use case is this: I have a multi-repo project and one of them returns the merged types. Until now I have simply passed them to createSchema(), but now I have to update to the latest nestjs/graphql version (I need the Root()-decorator).
Thanks,
Steven
I have seen those similar issues nestjs/nest#484, nestjs/nest#488 and they seem to be resolved. However, I am on @nestjs/graphql v3.0.0, @nestjs/common and /core v5.0.0 and the following code:
@Module({
imports: [GraphQLModule]
})
export class GraphQLSetupModule {
private readonly schema: any;
constructor(graphQLFactory: GraphQLFactory) {
this.schema = graphQLFactory.createSchema({
typeDefs: mergedTypes
});
}
}
where mergedTypes
is exactly:
schema {
query: Query
}
type Query {
countries: [Country]
}
directive @entity on OBJECT
type Country @entity {
# The id is also the official ISO code of the country.
_id: ID
name: String
}
fails with stack trace:
TypeError: Cannot convert undefined or null to object
at Function.getPrototypeOf (<anonymous>)
at ResolversExplorerService.filterResolvers (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/resolvers-explorer.service.js:34:34)
at resolvers.flatMap.instance (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/resolvers-explorer.service.js:27:66)
at map (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/resolvers-explorer.service.js:31:102)
at Array.map (<anonymous>)
at lodash_1.flattenDeep.modules.map.module (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/resolvers-explorer.service.js:31:80)
at Array.map (<anonymous>)
at ResolversExplorerService.flatMap (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/resolvers-explorer.service.js:31:45)
at ResolversExplorerService.explore (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/resolvers-explorer.service.js:27:32)
at GraphQLFactory.createSchema (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/graphql/dist/graphql.factory.js:23:149)
at new GraphQLSetupModule (/Users/danielkucal/Applications/someApp/src/LHBackend/dist/src/graphql/GraphQLSetupModule.js:27:38)
at resolveConstructorParams (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/core/injector/injector.js:64:84)
at Injector.resolveConstructorParams (/Users/danielkucal/Applications/someApp/src/node_modules/@nestjs/core/injector/injector.js:86:30)
at process._tickCallback (internal/process/next_tick.js:178:7)
Any ideas? Thanks in advance!
I'm submitting a...
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
I want to implement two endpoints. For this goal I have two modules: AdminModule and SiteModule. In each module I imported GraphQLModule:
GraphQLModule.forRootAsync({
useFactory: async () => {
return {
typePaths: ['./src/admin/**/*.graphql'],
path: '/admin',
}
},
})
and
GraphQLModule.forRootAsync({
useFactory: async () => {
return {
typePaths: ['./src/site/**/*.graphql'],
path: '/site',
}
},
})
In this case only /admin
is available. When I request /site
it returns 404. From another side I can use forRoot
instead of forFootAsync
. In this case both endpoints work as expected. But I have to use forRootAsync
for have possibility to define allowResolversNotInSchema: true
by the issue described in #19. Without It I get error: Error: "Mutation" defined in resolvers, but not in schema
when in shared module I add some resolver which defined only in one of two schemes.
Expected behavior
Possibility for implement multiple endpoints
Minimal reproduction of the problem with instructions
- Use with example https://github.com/nestjs/nest/tree/master/sample/12-graphql-apollo/src
- Add two modules with configs as described above.
What is the motivation / use case for changing the behavior?
It is very convenient for have possibility for split public and protected API.
Environment
Nest version: 5.3.0
For Tooling issues:
- Node version: 10.1.0
- Platform: Windows
I found an issue regarding guards. Let's take the following example:
import { Injectable, CanActivate, ExecutionContext } from '@nestjs/common';
import { Observable } from 'rxjs';
import { Reflector } from '@nestjs/core';
@Injectable()
export class RolesGuard implements CanActivate {
constructor(private readonly reflector: Reflector) {}
canActivate(context: ExecutionContext): boolean {
const roles = this.reflector.get<string[]>('roles', context.getHandler());
if (!roles) {
return true;
}
const request = context.switchToHttp().getRequest();
const user = request.user;
return user && user.role && roles.some((role) => role === user.role));
}
}
Now, in the rest of the framework this works like a charm. But whenever you are in graphql, this doesn't work quite as well. Taking the following .gql
file.
type Bookings implements Node {
id: ID!
...
}
type BookingEdge {
cursor: ID!
node: Booking
}
type BookingConnection {
edges: [BookingEdge]
nodes: [Booking]
pageInfo: PageInfo!
totalCount: Int!
}
type Restaurant implements Node {
id: ID!
orders(first: Int, after: String, last: Int, before: String):OrderConnection
...
}
type Query {
restaurant(id: ID!): Restaurant
}
For the following query, the const request = context.switchToHttp().getRequest();
becomes the user.
query ($id: ID!) {
restaurant(id: $id) {
id
bookings {
nodes {
id
}
}
}
}
So, in this query, request.user
in the guard, becomes undefined
and you have to make a workaround:
canActivate(context: ExecutionContext): boolean | Promise<boolean> {
const roles = this.reflector.get<string[]>('roles', context.getHandler());
const request = context.switchToHttp().getRequest(); //this works only for when querying a parent type
const ctx = context.getArgByIndex(2); // this works for when querying a child.
const user = request.user || ctx.user;
return user && user.role && roles.some((role) => role === user.role));
}
Can you guys check if it happens to you or it's an issue of mine? Thank you.
I'm submitting a...
[ ] Regression
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
typePaths
is mandatory and dominant, without it on graphql.mergeTypes it will throw an error.
Expected behavior
I should be able to use a pre-cooked schema out of the box.
Minimal reproduction of the problem with instructions
GraphQLModule.forRootAsync({
imports: [
TypeGQLModule.forSchema({
resolvers: [
DefaultResolver,
...ModuleLocator.flattenModuleField('resolvers')
],
pubSub,
authChecker
})
],
async useFactory(graphQL: GraphQlBridge): Promise<GqlModuleOptions> {
const schema: GraphQLSchema = graphQL.buildSchema()
const playground: any = {
settings: {
'editor.cursorShape': 'line'
}
}
return {
schema,
introspection: true,
tracing: true,
context: ({ req, res }) => ({
req,
res
}),
playground
}
},
inject: [GraphQlBridge]
})
],
It failed with:
Error: Specified query type "Query" not found in document.
at E:\typescript-starter\node_modules\graphql\utilities\buildASTSchema.js:184:15
at Array.forEach (<anonymous>)
at getOperationTypes (E:\typescript-starter\node_modules\graphql\utilities\buildASTSchema.js:177:27)
at Object.buildASTSchema (E:\typescript-starter\node_modules\graphql\utilities\buildASTSchema.js:127:36)
at Object.buildSchemaFromTypeDefinitions (E:\typescript-starter\node_modules\graphql-tools\dist\generate\buildSchemaFromTypeDefinitions.js:24:28)
at Object.makeExecutableSchema (E:\typescript-starter\node_modules\graphql-tools\dist\makeExecutableSchema.js:27:29)
at GraphQLFactory.mergeOptions (E:\typescript-starter\node_modules\@nestjs\graphql\dist\graphql.factory.js:30:98)
at Function.<anonymous> (E:\typescript-starter\node_modules\@nestjs\graphql\dist\graphql.module.js:73:55)
at Generator.next (<anonymous>)
at E:\typescript-starter\node_modules\@nestjs\graphql\dist\graphql.module.js:19:71
at new Promise (<anonymous>)
at __awaiter (E:\typescript-starter\node_modules\@nestjs\graphql\dist\graphql.module.js:15:12)
at Object.useFactory [as metatype] (E:\typescript-starter\node_modules\@nestjs\graphql\dist\graphql.module.js:71:68)
at resolveConstructorParams (E:\typescript-starter\node_modules\@nestjs\core\injector\injector.js:68:55)
at Injector.resolveConstructorParams (E:\typescript-starter\node_modules\@nestjs\core\injector\injector.js:99:30)
at process._tickCallback (internal/process/next_tick.js:68:7)
What is the motivation / use case for changing the behavior?
I used MagnusCloudCorp/nestjs-type-graphql instead of the helpers from @nestjs/graphql
provided out of the box and TypeGraphQL provided a compiled schema instead of SDL.
Environment
Extra info
This is the reason it failed:
|
mergeOptions(options: GqlModuleOptions = { typeDefs: [] }): GqlModuleOptions { |
|
const resolvers = extend( |
|
this.scalarsExplorerService.explore(), |
|
this.resolversExplorerService.explore(), |
|
); |
|
return { |
|
...options, |
|
typeDefs: undefined, |
|
schema: makeExecutableSchema({ |
|
resolvers: extend(resolvers, options.resolvers), |
|
typeDefs: gql` |
|
${options.typeDefs} |
|
`, |
|
}), |
|
}; |
|
} |
My schema option, no matter what are always gonna be
Object.assign
'd
Following code
const typeDefs = this.graphQLFactory.mergeTypesByPaths(
`src/@core/**/*.graphqls`,
`src/${process.env.APP_NAME}/**/*.graphqls`
);
will only generate type definitions for first pattern: src/@core/**/*.graphqls
, all next patterns not merged.
Manual merging fixes this issue:
import { fileLoader, mergeTypes } from 'merge-graphql-schemas';
const coreTypes = fileLoader(`src/@core/**/*.graphqls`);
const appTypes = fileLoader(`src/${process.env.APP_NAME}/**/*.graphqls`);
const types = coreTypes.concat(appTypes);
const typeDefs = mergeTypes(types);
Does anybody know how to solve this problem?
Trying to configure GraphQL subscriptions using existing express server.
But seems that there is some kind of conflict.
Error thrown in graphiql
console:
WebSocket connection to 'ws://localhost:3000/subscriptions' failed: Connection closed before receiving a handshake response

When using new server. There is no error.
Here the graphQL configuration I've used:
this.setSameServer()
- uses nest http server instance.
this.setDifferentServer()
- uses new http instance.
import {
MiddlewareConsumer,
Module,
HttpServer,
Inject,
NestModule,
OnModuleDestroy,
} from '@nestjs/common';
import { AppController } from 'app.controller';
import { AppService } from 'app.service';
import { graphqlExpress, graphiqlExpress } from 'apollo-server-express';
import { GraphQLModule, GraphQLFactory } from '@nestjs/graphql';
import { AuthorResolver } from 'author.resolver';
import { SubscriptionServer } from 'subscriptions-transport-ws';
import { execute, subscribe } from 'graphql';
import { createServer } from 'http';
import { HTTP_SERVER_REF } from '@nestjs/core';
@Module({
imports: [GraphQLModule, AuthorResolver],
controllers: [AppController],
providers: [
{
provide: 'SUBSCRIPTION_SERVER',
useFactory: () => {
const server = createServer();
return new Promise(resolve => server.listen(88, () => resolve(server)));
},
},
AppService,
],
})
export class AppModule implements NestModule, OnModuleDestroy {
private subscriptionServer: SubscriptionServer;
private subscriptionPort: number;
private wsServer: HttpServer;
constructor(
private readonly graphQLFactory: GraphQLFactory,
@Inject(HTTP_SERVER_REF) private readonly httpServerRef: HttpServer,
@Inject('SUBSCRIPTION_SERVER') private readonly ws: HttpServer,
) {
this.setSameServer();
//this.setDifferentServer();
}
private setSameServer() {
this.wsServer = this.httpServerRef.getHttpServer();
this.subscriptionPort = 3000;
}
private setDifferentServer() {
this.wsServer = this.ws;
this.subscriptionPort = 88;
}
public configure(consumer: MiddlewareConsumer) {
const typeDefs = this.graphQLFactory.mergeTypesByPaths('./**/*.graphql');
const schema = this.graphQLFactory.createSchema({ typeDefs });
const route = '/graphql';
const routeIDE = '/graphiql';
const routeSubs = '/subscriptions';
const middlewareIDE = graphiqlExpress({
endpointURL: route,
subscriptionsEndpoint:
'ws://localhost:' + this.subscriptionPort + routeSubs,
});
const middleware = graphqlExpress(req => ({
schema,
rootValue: req,
debug: false,
}));
consumer.apply(middleware).forRoutes(route);
consumer.apply(middlewareIDE).forRoutes(routeIDE);
this.subscriptionServer = new SubscriptionServer(
{
execute,
subscribe,
schema,
},
{
server: this.wsServer,
path: routeSubs,
},
);
}
public onModuleDestroy() {
this.subscriptionServer.close();
}
}
Used these issues for help:
nestjs/nest#500
#6
And full repo if you want to reproduce:
https://github.com/ph55/nest-graphql-subscriptions
Is there any way to add @Body to this library for the args param. Finding it frustrating having to convert POJO's from inputs to TypeScript classes.
Hello,
Is there any good way to validate data in mutations like string length etc?
typescript mutation { createSth(name:"something", website:"http://test.com/") { id name website } }
How can i validate name or website data?
PS: Kamil, great job with nestjs!
Regards
Here is a good example on how to apply Auth in GraphQL using Directive Resolvers as "resolvers middlewares" -> https://blog.graph.cool/graphql-directive-permissions-authorization-made-easy-54c076b5368e. Currently this module don't support to define directives, even that graphql-tools
allows it.
I don't know how that is handled in combination with Guards/Interceptors of Nest. Using this kind of directives allow the Schema definition to be discovered by the users and depending the role to show or hide specific fields.
I'm submitting a...
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
import graphqlPlayground from 'graphql-playground-middleware-express';
// ...
consumer
.apply(
// Here the error happens
graphqlPlayground({
endpoint: '/graphql',
subscriptionsEndpoint: `ws://localhost:5001/subscriptions`
})
)
.forRoutes('/graphiql')
.apply(
graphqlExpress(async req => ({
schema,
rootValue: req,
context: req,
formatError: (error: GraphQLError) => {
return error.originalError instanceof BaseException ? error.originalError.serialize() : error;
}
}))
)
.forRoutes('/graphql');
(node:10937) UnhandledPromiseRejectionWarning: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
at ServerResponse.setHeader (_http_outgoing.js:471:11)
at ServerResponse.header (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/express/lib/response.js:767:10)
at ServerResponse.send (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/express/lib/response.js:170:12)
at ServerResponse.json (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/express/lib/response.js:267:15)
at ExpressAdapter.reply (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/@nestjs/core/adapters/express-adapter.js:41:52)
at ExceptionsHandler.next (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/@nestjs/core/exceptions/exceptions-handler.js:33:29)
at /Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/@nestjs/core/router/router-proxy.js:12:35
at Layer.handle [as handle_request] (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/express/lib/router/index.js:317:13)
at /Users/cschroeter/Workspace/Playground/graphql-yoga/nest-yoga/node_modules/express/lib/router/index.js:284:7
Expected behavior
Instead of the classic GraphiQL UI, I would like to use the superior graphql-playground-middleware-express
Environment
"@nestjs/common": "5.0.1",
"@nestjs/core": "5.0.1",
"@nestjs/graphql": "3.0.0",
"@nestjs/mongoose": "5.0.0",
"@nestjs/passport": "1.0.10",
"@nestjs/testing": "5.0.1"
For Tooling issues:
- Node version: 10.2.1
- Platform: Mac OS
how to test graphql use nestjs
I'm submitting a...
Current behavior
In the interface GqlModuleOptions
, the typeDefs
property is inherited from the apollo-server Config
interface, which defines it as typeDefs?: DocumentNode | Array<DocumentNode>;
However, when I pass a DocumentNode as the value of typeDefs
, I get the following error:
[Nest] 15752 - 2018-9-3 16:43:12 [ExceptionHandler] Syntax Error: Unexpected [ +102ms
Syntax Error: Unexpected [
GraphQL request (5:2)
4: }
5: ,[object Object]
^
6:
at syntaxError (C:\Development\vendure\vendure\server\node_modules\graphql\error\syntaxError.js:24:10)
at unexpected (C:\Development\vendure\vendure\server\node_modules\graphql\language\parser.js:1485:33)
at parseDefinition (C:\Development\vendure\vendure\server\node_modules\graphql\language\parser.js:160:9)
at parseDocument (C:\Development\vendure\vendure\server\node_modules\graphql\language\parser.js:115:22)
at parse (C:\Development\vendure\vendure\server\node_modules\graphql\language\parser.js:48:10)
at parseDocument (C:\Development\vendure\vendure\server\node_modules\graphql-tag\src\index.js:129:16)
at Object.gql (C:\Development\vendure\vendure\server\node_modules\graphql-tag\src\index.js:170:10)
at GraphQLFactory.mergeOptions (C:\Development\vendure\vendure\server\node_modules\@nestjs\graphql\dist\graphql.factory.js:32:55)
at Function.<anonymous> (C:\Development\vendure\vendure\server\node_modules\@nestjs\graphql\dist\graphql.module.js:73:55)
at Generator.next (<anonymous>)
Passing a string representation of the schema on the other hand works, but then I need to cast the string to any
to avoid type errors.
This line in the GraphQLFactory
class seems to be the point that the value is used as a string (or array of strings to be exact):
|
typeDefs: gql` |
|
${options.typeDefs} |
|
`, |
Expected behavior
Either the GraphQLFactory should perform a check to see if the typeDefs
is a DocumentNode, and if so then skip the gql
tag call.
Or just change the GqlModuleOptions
to make typeDefs a string type.
Environment
Nest version: 5.3.0, graphql v5.1.0
I'm submitting a...
[X] Regression
[X] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
I can't access the request within my guards anymore. The request within the execution context is always undefined. It looks like the request doesn't get passed through apollo server correctly.
Expected behavior
The request should be accessible within guards.
Minimal reproduction of the problem with instructions
https://github.com/w0wka91/nest/tree/graphql-passport-integration
What is the motivation / use case for changing the behavior?
The request should be accessible to authenticate the user. Furthermore this behavior doesn't let me integrate nestjs/passport into my application.
Environment
Nest version: 5.3.0
This error accurs since apollo server was updated
For Tooling issues:
- Node version: 10.9
- Platform: Mac
Others:
This syntax is not working in the NPM version. Probably a release is pending.
const resolvers = {
UUID: GraphQLUUID
}
const typeDefs = this.graphQLFactory.mergeTypesByPaths('./**/*.graphql');
const schema = this.graphQLFactory.createSchema({ typeDefs, resolvers });
Does this package support Apollo Server 2.0 or the older version? I installed their release candidate for express ([email protected]). graphqlExpress is no longer available. import { graphqlExpress } from 'apollo-server-express';
How would I go about using nestjs/graphql with Apollo Server 2.0?
thank you
My AppModule have this configuration https://docs.nestjs.com/graphql/quick-start, but a need to upload a file with multipart/form-data, i added a new Module with a Controller with this method:
@Post('upload') @UseInterceptors(FileInterceptor('file', { storage })) async uploadFile(@UploadedFile() file, @Response() res) { return {}; }
this method never respond to a client
If the parent resolver and the child resolver both have Guard, the validate function of the guard will be triggered twice. The guard of parent will be passed with the request object, while the guard of the child will be passed with whatever parent resolver returns.
@Resolver('User')
export class UserResolvers {
constructor(
private readonly userService: UserService
) {}
@UseGuards(CustomGuard) // validate function here will get request object
@Query('me')
async getUser(obj, args, context, info) {
const { user } = context
return {
account_type: user.accountType,
balance: user.balance,
currency: user.currency,
id: user.accountId
}
}
@UseGuards(CustomGuard) // validate function here will get the result of getUser
@ResolveProperty('balance')
async getBalance(obj, args, context, info) {
if (obj.balance) return obj.balance
const data = await this.userService.getAccount(context, context.user.session)
return data.balance
}
}
Since apollo-server-express
is not working in the Nest way, a new middleware, that adapts to the Exception handling of Nest should be created. The original issue was created in @nestjs/nest
since the example in the documentation leads to use this library.
Related issue nestjs/nest#556
With @nestjs/graphql, how to generate document for graphql api ?

There is No Description.
Example:
`import { Query, Resolver } from '@nestjs/graphql';
@resolver('Example')
export class ExampleResolvers {
constructor() {
}
@query('example')
async example(obj, args, context, info) {
return {name: 'alik'};
}
async otherMethod() {
return 'hello word';
}
}
`
y have this error (node:8600) UnhandledPromiseRejectionWarning: Error: Example.otherMethod defined in resolvers, but not in schema
I'm submitting a...
[ x] Documentation issue or request
On the documentation of Graphql there is nothing talking about Batching or Caching
https://www.npmjs.com/package/dataloader
Is there any example integrating this or get a same behavior with nestjs?
Very excited about NestJS. Thinking of becoming a sponsor if it proves out for my new project.
I need to get GraphQL subscriptions working. For starters, I've implemented the example from docs, and now I'm trying to connect GraphiQL with something like this:
consumer
.apply(graphiqlExpress({
endpointURL: "/graphql",
subscriptionsEndpoint: `ws://localhost:${process.env.PORT || 3000}/subscriptions`
}))
.forRoutes({path: "/graphiql", method: RequestMethod.GET})
.apply(graphqlExpress(req => ({schema, rootValue: req})))
.forRoutes({path: "/graphql", method: RequestMethod.ALL});
I'm getting ERR_CONNECTION_REFUSED
in browser console. I feel like I'm missing the connection between GraphQL Subscriptions and WebSockets, but I can't seem to piece it together from the docs.
Are there any working e2e examples out there?
I'm trying to migrate my old nestjs app with graphQL to new GraphqlModule. And i faced with problem how to define resolver for scalar type, previously i had:
scalar Date
type User {
_id: ID!
fullName: String
email: String
hireDate: Date
pictureUrl: String
}
import { GraphQLScalarType } from 'graphql';
import { Kind } from 'graphql/language';
export const resolver = {
Date: new GraphQLScalarType({
name: 'Date',
description: 'Date custom scalar type',
parseValue(value) {
return new Date(value); // value from the client
},
serialize(value) {
return value.getTime(); // value sent to the client
},
parseLiteral(ast) {
if (ast.kind === Kind.INT) {
return parseInt(ast.value, 10); // ast value is always in string format
}
return null;
}
})
};
So how do i define resolver for Date type using nestjs annotations ?
I've tried this but it doesn't work
@Resolver('Date')
export class DateResolver {
@DelegateProperty('Date')
getDate() {
return new GraphQLScalarType({
name: 'Date',
description: 'Date custom scalar type',
parseValue(value) {
return new Date(value); // value from the client
},
serialize(value) {
return value.getTime(); // value sent to the client
},
parseLiteral(ast) {
if (ast.kind === Kind.INT) {
return parseInt(ast.value, 10);
}
return null;
}
});
}
}
Recommend Projects
-
-
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
An Open Source Machine Learning Framework for Everyone
-
The Web framework for perfectionists with deadlines.
-
A PHP framework for web artisans
-
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
Some thing interesting about web. New door for the world.
-
A server is a program made to process requests and deliver data to clients.
-
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Some thing interesting about visualization, use data art
-
Some thing interesting about game, make everyone happy.
-
Recommend Org
-
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Open source projects and samples from Microsoft.
-
Google ❤️ Open Source for everyone.
-
Alibaba Open Source for everyone
-
Data-Driven Documents codes.
-
China tencent open source team.
-