Skip to content
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

can not use objectype as field return type in serverless offline environment #1585

Closed
myfreax opened this issue Jun 15, 2021 · 1 comment
Closed

Comments

@myfreax
Copy link

myfreax commented Jun 15, 2021

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.

I try resolve this error with this issue type-graphql-isssue-96, type-graphql-issue-396. But finally failed to solve this error

Current behavior

yarn sls:offline start app. After you will see this error

offline: Failure: Schema must contain uniquely named types but contains multiple types named "Task".
Error: Schema must contain uniquely named types but contains multiple types named "Task".

When you start app with command yarn start. This will any error output

Expected behavior

No any error output like yarn start

Minimal reproduction of the problem with instructions

The example repo is here nest-serverless-offline-debug

What is the motivation / use case for changing the behavior?

Environment


Nest version: 7.6.0

 
For Tooling issues:
- Node version: v14.17.0  
- Platform:  
Description:    Ubuntu 20.04.2 LTS
Release:        20.04
Codename:       focal

Others:

@kamilmysliwiec
Copy link
Member

This doesn't seem to be an issue with the package itself, but rather with your setup & project configuration.

Please, use our Discord channel (support) for such questions. We are using GitHub to track bugs, feature requests, and potential improvements.

@nestjs nestjs locked and limited conversation to collaborators Jun 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants