cesarve77/mandarina

full-stack React+GraphQL+Prisma.io library

mandarina's Issues

Docs

import {CreateForm} from 'mandarina' import '/app/lib/tables/Post' export default ()=> <CreatePostForm table={Post}/>
Is there a typo in the docs. Or that's the way it's suppose to be.
I was using it in this way <CreateForm table={Post}/>.

option name are duplicate

Now there in as option name in Table and Schema.

Check what happens when are diferents

Update Form Mutation is sending `first: 50` in input payload

The mutation generated by <UpdateForm /> is inserting first: 50 in the input payload

{"operationName":"mutationFn","variables":{"where":{"id":"cjxcmchik00330791n4y3vvl3"},"first":50,"data":{"id":"cjxcmchik00330791n4y3vvl3","name":"Eduardo Zarraga M","email":"[email protected]","avatar":null}},"query":"mutation mutationFn($where: UserWhereUniqueInput!, $data: UserUpdateInput!) {\n updateUser(data: $data, where: $where) {\n id\n name\n email\n avatar\n __typename\n }\n}\n"}

Create new table

If we remove table it stays in the prisma even though it is no longer in our yoga server. I think table should be deleted from prima as well.

Need to add `id` in `omitFields` to perform a mutation using <UpdateForm />

if the id is not added in the omitFields prop of ` it will throw a bad request with the following error

Variable "$data" got invalid value { id: "cjxcmchik00330791n4y3vvl3", name: "Eduardo Zarraga", email: "[email protected]", avatar: null }; Field "id" is not defined by type UserUpdateInput

Missing action

When a form action call a no existing action (or not registered)
there no error, conversely call a empty resolver

Validate object values received for the resolvers

We need validate de object values against validators. values like minNumber, RegEx and rest.

We already have a validator in Schema, but the object received for the resolver will have properties like: 'create', 'update' and 'connect' coming from prisma semantic.

Or we do a new validator, which check the prisma semantic as well or we transform the object removing that properties and after check it with the existing validate function

defaultValue in schema is always setting the same value

default value in a schema prop { type: Boolean, defaultValue: false } is always setting a fixed value for the uniform model.