You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My application's schema is in the neighborhood of 200 enums + models. I have multiple files which get concatenated together to form schema.prisma:
a.prisma + b.prisma + c.prisma = schema.prisma
In reality they're named according to functional areas.
The concatted file is absolutely valid, but when working with any one file it may refer to models from other files and the linter complains it's unknown.
Suggested solution
I would like the ability to end lines with something like //// prisma-language-server ignore-next-line which I could easily filter out in my concat step but could disable linting for that line.
Alternatives
Even better to have first class multi file support. A subset of possibilities include
#include "a.schema" style directive
model ModelName @import "a.schema:ModelName"; decorator
But I think either of these would require work not just on the linter's part but within the prisma schema spec itself so quickly a much larger lift
Additional context
The lint errors don't block my use of the extension, they just raise false positives.
The text was updated successfully, but these errors were encountered:
Problem
My application's schema is in the neighborhood of 200 enums + models. I have multiple files which get concatenated together to form schema.prisma:
a.prisma + b.prisma + c.prisma = schema.prisma
In reality they're named according to functional areas.
The concatted file is absolutely valid, but when working with any one file it may refer to models from other files and the linter complains it's unknown.
Suggested solution
I would like the ability to end lines with something like
//// prisma-language-server ignore-next-line
which I could easily filter out in my concat step but could disable linting for that line.Alternatives
Even better to have first class multi file support. A subset of possibilities include
#include "a.schema"
style directivemodel ModelName @import "a.schema:ModelName";
decoratorBut I think either of these would require work not just on the linter's part but within the prisma schema spec itself so quickly a much larger lift
Additional context
The lint errors don't block my use of the extension, they just raise false positives.
The text was updated successfully, but these errors were encountered: