Following the tutorial, ends in a not working state.

The problem arises when using the command "prisma deploy" for the first time.

https://www.howtographql.com/react-apollo/1-getting-started/

https://github.com/howtographql/howtographql/blob/master/content/frontend/react-apollo/1-getting-started.md

Section: Backend
Subsection: Deploying the Prisma database service

The commands

This issue pertains to the following package(s):

• GraphQL Playground - Electron App
• GraphQL Playground HTML
• GraphQL Playground
• GraphQL Playground Express Middleware
• GraphQL Playground Hapi Middleware
• GraphQL Playground Koa Middleware
• GraphQL Playground Lambda Middleware

The default value of request.credentials is "omit". The differs from th

The api server and webpack dev server should be restarted when the redwood.toml configuration is modified.

Related: #478

https://www.npmjs.com/package/@prisma/cli and https://www.npmjs.com/package/@prisma/client could use some love <3

EDIT: See this comment below on what to document.

What is the problem?

Cannot add dependencies to packages

Steps to Reproduce:

1. Pull canary
2. yarn
3. cd ./examples/server
4. yarn add --dev metro-memory-fs
5. Get Yarn error:

blitz/packages/server on  canary [$] via ⬢ v12.16.1

Right now Actions reports the tests are succeeding, although they are clearly failing:

prisma/prisma-examples#1652
prisma/prisma-examples#1651

That is dangerous, as one does not really see when stuff goes wrong.

Fundamentally there are 2 problems:

1. All tests are run in one batch, a suggestion to change that is at https://github.com/p

Many of the controllers & services do not have tests written. These would be helpful to include as examples of how to handle testing.

perhaps a little confusing about why src and queries are sibling directories, as src also contains some .graphql too

Thanks @rarkins for this feedback. Would be great to hear other suggestions.

Any idea when parameterized count queries will be built into nexus generated GQL queries? prisma/prisma-client-js#252

Asking before I build it out myself, or try and build it out here and open a PR.

The graphqlgen prepare step fails on yarn setup:prisma

shop (mashop (master) λ  yarn setup:prisma
yarn run v1.12.3
$ cd api && yarn deploy:local && yarn seed:local
$ docker-compose -f database/docker-compose.yml up -d && prisma deploy && graphql prepare
database_mysql_1 is up-to-date
database_prisma_1 is up-to-date
Deploying service `shop` to stage `local` to server `local` 39ms
S

I only using this for language syntax.

Actual Behavior

• Opening, creating, editing and saving graphql files results in an error

Expected Behavior

• View graphql with language mode
• Being able to open, create, edit and save file without error

Steps to Reproduce the Problem Or Description

• Create profile, specifically I have an aws amplify project
• add api to proj

The current UI's for those are really prototypes so that I could continue the RN app. They definitely needs to be done in a better way, mostly in terms of UI. The UX is already kind of good.

Hi,

And congrats for this library!

It would improve discoverability if you added a link to your repository in the react-admin documentation, in the Data Providers section.

Currently, Prisma does not have a cross-database PrismaClient (Seehttps://github.com/prisma/prisma/issues/1487).

This means that once we set a provider for the first tenant, all other tenants will have to use the same provider.

There is two ways to handle this issue:

1. Wait for Prisma to have a cross-database Photon (not sure if/when this will happen)
2. Use prisma-multi-tenant to add a