Error: Required named parameter 'logEmitter' must be provided. about prisma-dart

[medz]

@Rodsevich You try to rerun the dart run orm generate command to fix the problem.

[Rodsevich]

yeah, I ran:

dart pub get
dart run orm generate
dart run build_runner build --delete-conflicting-outputs

I had to edit the code to

final _i2.Engine engine = _i2.BinaryEngine(
      logEmitter: _i2.PrismaLogEmitter([]),

to have the project built

[medz]

@Rodsevich

Can you provide a minimal reproduction example? I created a new Dart project and then used your command steps and still haven't found the problem.

[Rodsevich]

Our schema.prisma begins with:

generator client {
  provider        = "prisma-client-dart"
  previewFeatures = ["interactiveTransactions"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL_WITH_SCHEMA")
}

model Entity {

[medz]

2.mov

[Rodsevich]

https://pastebin.com/73SS2sJB
This is the schema.prisma we have. If the bug doesn't replicate with that, do you know a way I can get rid of it on the project?

[medz]

This problem doesn't seem to be related to the schema, you try to regenerate the client after changing the orm version to 2.3.1 in pubspec.yaml. I'll copy your schema and keep trying.

[medz]

I copied your schema to try. There were no problems either. Can I see the contents of your pubspec.yaml?

[Rodsevich]

Sure!
https://pastebin.com/EVCXTXUC

[medz]

Sorry, I still haven't found the bug. Prisma Client's logging field generation does not depend on schema, but this feature does confirm inclusion in version 2.3.1.

I suspected a Schema issue at first, after testing it wasn't. Then I suspected a dependency conflict or something, and found that it wasn't. Got it to work without issue on my computer as well as in the docker container.

This may require you to help debug:

1. Remove the orm dependency (dart pub rmeove orm) from your project and re-depend on it (dart pub add orm), if the bug still exists, try 2.
2. Create a new Dart project that depends on the orm package. Then generate the client whether the problem still exists. If this bug persists, please run dart --version and report the output to me. I will find the same version information for a targeted fork test.