deps: upgrade to latest prisma & fix tests

[jasonkuhrt]

closes #78

[codecov-commenter]

Codecov Report

Merging #85 (3db027a) into main (7d1c18d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #85   +/-   ##
=======================================
  Coverage   44.82%   44.82%           
=======================================
  Files          26       26           
  Lines         406      406           
  Branches       80       80           
=======================================
  Hits          182      182           
  Misses        205      205           
  Partials       19       19           

[jasonkuhrt]

@janpio @Jolg42 It used to be that this worked. The prisma client was specified to be output at ./client or something. After a Prisma upgrade 2704ff2 to 2.24 tests began to break.

  execa.commandSync(`yarn -s prisma db push --force-reset --schema ${dir}/schema.prisma`)

I fixed this once using Jest runInBand. The commit above. That tells me that two Jest test suites were conflicting. And indeed the test error output indicates snapshots failing with results from one another.

Having to use runInBand is a hack, not ideal etc. It is also not a big deal. The worst of it is using it when not knowing why, as is the case now.

I am going to try to change execa (shown above) to run so that it is actually spawning the child process IN the dir, rather than given a path to the schema in the dir. I am betting that will get things working again, how they used to, without runInBand.

[jasonkuhrt]

@Jolg42 maybe the issue was how prisma schema output relative paths were resolved? I have been doing output = './client' so far.

[jasonkuhrt]

My solution worked I think, but the relative path stuff isn't working on Windows. https://github.com/prisma/nexus-prisma/pull/85/checks?check_run_id=2879192617 I thought it might not. Will try relative path another way. But first will try absolute output config.

[jasonkuhrt]

I have no idea what is going on, the macos tests pass on everything but then hang on trying to run the next integration test.

When I run in band, there is no issue.

On my machine, there is no issue.

:(

Well, I did my best, here comes runInBand at least for now.

[Jolg42]

Might be related to @millsp PR I think

Probably fixed with prisma/prisma#7797?

[rostislav-simonik-nexus-prisma-admin]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• npm package (@next-major dist-tag)
• GitHub release

Your semantic-release bot 📦🚀