
                    For controllers, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

This was a hard one to track down with an annoying fix (Nest specific not the fault of type-graphql) 

type graphql Getting "Schema must contain uniquely named types but contains multiple types named" for a single type

For future readers
This may have been due to using an @ObjectType() CompanyData   as an @InputType() in the resolver See docs for: inputType 

type graphql Cannot determine GraphQL input type for

Hi @19majkel94! We're still very interested in supporting you with a seamless Prisma integration Given the very nature of developers 

type graphql Integration with Prisma

@darkmantle
Setting:

Means you should use default import: The latest version (0.15.0) seems to have issues with custom scalars such as the JSON type provided by the GraphQLJSON package (graphql-type-json)