Shea Belsky

I was able to get around this by manually implementing a portal, then conditionally rendering the element within the panel based on whether or not it was expanded! ```js const...

@rexih I couldn't use that line as-is, it needs to be formatted in `pubspec.yaml` file a little differently for it to work. Each line with a colon needs to be...

Potentially related issues: * https://github.com/Azure/azure-quickstart-templates/issues/3319 * https://github.com/Azure/azure-quickstart-templates/issues/3813 * https://github.com/Azure/azure-quickstart-templates/issues/2632

@faustinozanetto I got this to work by installing the `@babel/plugin-transform-modules-commonjs` Babel plugin. I plan on uploading a minimal viable GitHub repo which includes everything (NextJS, TypeGraphQL, Prisma) over the next...

@jctaoo Hmm I hadn't noticed that before, but now I can see that problem happening. That's strange, not sure what could be causing that.

@jctaoo Here's my minimally viable repo: https://github.com/SheaBelsky/nextjs-prisma-typegraphql So far I'm not running into the issue where changing one component causes Next to completely reload everything. I'm not sure what triggers...

Because of the scope of this change, is there a reason this particular release was not marked as a breaking change (`1.0.0`)? Does `typegraphql-prisma` follow semver for versioning?

TIL - sorry for my initial misunderstanding!

Anecdotally, one thing that resolved this issue for me was pinning the TypeScript binary used by VS Code to be whatever was installed locally. Make a file at `.vscode/settings.json` with...

@devevignesh It's yours! Thank you for picking this up!