Gabriel Colson

Hello @ThomasAribart The current typescript implementation is unusable because of the type complexity which mainly comes from the API, as you noted. I agree the API needs to be reworked...

Hello everyone I don't have the time to work on this plugin anymore. Feel free to open a PR I would be happy to review and merge it

Hello! There is a [`prisma format`](https://github.com/prisma/specs/tree/master/schema#auto-formatting) command that does exactly that. I will take a look at how to integrate this in the plugin but in the meantime, you should...

Thanks for letting me know! I will definitely look into that as it will avoid duplication of the work on the syntax parsing.

Hey @Denu8thell! I already dived into the doc of this project and tried to make a small PoC. Before I start to properly integrate it, I still have to figure...

Sounds great! Thank you! 😄

Thank you for your feedback. This kind of feature will need the implementation of code references and I am planning to explore this soon ;)

That means you will get a lot of duplicated external events in both X and Y event lakes. Or should we not store external events to the event lakes ?

Thanks for you insights. In case you have multiple downstream subsystems, do you still replay events in the egress? We usually have an idempotency table in ingresses that expires records...

Hi @Lewenhaupt My tsconfig.json: ```json { "compilerOptions": { "alwaysStrict": true, "declaration": true, "esModuleInterop": true, "experimentalDecorators": true, "inlineSourceMap": true, "inlineSources": true, "lib": [ "es2019" ], "module": "CommonJS", "noEmitOnError": false, "noFallthroughCasesInSwitch": true,...