Darryl
11/28/2019, 9:54 AMconst User = prismaObjectType({
name: "User",
definition(t) {
t.prismaFields({
filter: ["createdAt", "updatedAt", "something", "somethingElse"]
})
}
})
Darryl
11/28/2019, 10:43 AMcategories
, is the Category
type not auto-generated for me based on my schema.prisma
in the first place?Darryl
11/28/2019, 1:46 PMobjectType
for a more complex type, I have to first list the fields I want to expose like this – t.model.someField()
– but for other, more complex fields (those using enums or other types), I also then have to create types manually for those and make sure they're all passed to makeSchema
? I thought these were generated in /node_modules/@prisma/photon/index.d.ts
. Can they not be used here? Apologies if I'm missing the big picture here. 🙂bastian
11/29/2019, 9:45 PMconfig
is undefined
tried to run in locally, some errors in console, but it works (though not after yarn website
but running yarn build
in website beforehandStefan
12/10/2019, 2:07 PMAashish Jain
12/13/2019, 9:33 PMhuv1k
12/16/2019, 4:23 PMNexus
plugins. 🤔Layton
12/16/2019, 11:37 PMLayton
12/16/2019, 11:38 PMtypegenAutoConfig: {
contextType: 'Context.Context',
sources: [
{
source: '@prisma/photon', // here?
alias: 'photon',
},
{
source: require.resolve('./context'),
alias: 'Context',
},
],
},
Awey
12/18/2019, 12:44 PMLayton
12/18/2019, 11:58 PMcreateOne...
mutation, and I want to refine given arguments of createInput
passed by mutation call(or add some extra logic into that resolver)Layton
12/19/2019, 2:24 AMAwey
12/19/2019, 2:37 PMzinger
12/23/2019, 5:11 PMresolve
behavior of a mutation, but keep all arguments, etc. the same, is my best option to use a single “data” arg
with type createThingInput
? Am I correct in understanding that once I want to simplify things like the arguments (break them out instead of having on “data” arg), I just have to re-implement the whole thing? Thanks!Rashmi Bidanta
01/02/2020, 9:28 PMmakeRemoteExecutableSchema
to build a schema from prismaRashmi Bidanta
01/02/2020, 9:29 PMErrorname
01/08/2020, 9:44 AMcsamu
01/12/2020, 2:34 PMprismaObjectType
and t.prismaFields
still used?
They are mentioned in the blog
https://www.prisma.io/blog/using-graphql-nexus-with-a-database-pmyl3660ncst#the-nexus-prisma-plugin-under-the-hoodLayton
01/14/2020, 12:54 AMgraphql-nexus
?Layton
01/14/2020, 12:55 AMapollo-server
howevrer not sure about nexus way to do thishuv1k
02/01/2020, 7:03 PMjasonkuhrt
nexus
package. I’ll let you read more through the link. https://github.com/prisma-labs/nexus/issues/373. Feedback more than welcome but preferably on the Github issue, thanks!Hugo Hammarström
02/08/2020, 3:09 PMCannot convert undefined or null to object
when using computed inputs on upsert mutations. Are computed inputs not supported for upsert mutations?Gabriel Colson
02/09/2020, 11:58 PMnpx nexus-future
does not work for me when I opt in for a database:Henry
02/10/2020, 10:03 PMRMCS
02/19/2020, 10:28 PMuserId
i'm generating all the different types etc and build my schema with the following setting
plugins: [nexusPrismaPlugin(
{
computedInputs: {
user: ({ ctx }) => ({ connect: { id: ctx.userId } }),
company: ({ ctx }) => ({ connect: { id: ctx.companyId } }),
}
}
)],
With this setting all relational fields are automaticly set, but are also removed from queries ex; relations(where: {*user_is_missing_here*})
so i cant get it it.. i want to filter it in my nodeJS backendKyle (TechSquidTV)
02/19/2020, 10:54 PMRMCS
02/20/2020, 7:53 AMAlex Vilchis
02/27/2020, 12:41 AMlogin
and signup
operations public.
Does anyone have an example?Mitchell Romney
03/02/2020, 1:21 AM$exists
within a query resolver's ctx
? Something like ctx.prisma.$exists.user(...)
doesn't seem to work.