"Hidden" schema error (?) causing cascading import failures
I had a feature branch working, with large numbers of code and schema changes. I switched branches, causing consternation in prisma & generated a migration and blew away the database in order to run. I did some other work in master, now I've switched back to the feature branch and made (another) migration for the same thing...
Now I am getting a seemingly endless series of errors on code which isn't changed by this branch, all of the form "import foo from '../somewhere/somthing".
It seems if I modify the import path in some way, like, say if it was "../server/foo" but we are already in the server directory, I can change it to "./foo" - which is technically the same directory, then we get past that error. Then another seemingly random import from another file (which used to work), is now failing, it seems the compilation stops on the first broken import & many are broken. I can sweep through many files which should not need to be changed, and seemingly never clear this. Wasp clean / wasp build does not change the outcome.
I believe this is related to a schema change, because had this same scenario ≈ two weeks ago and had to hand-merge-file-by-file until I -finally- got an error message related to schema which I fixed - and this problem went away. I forget what that issue was, but this is the same symptom.
What could be the issue @kapa.ai ?
Now I am getting a seemingly endless series of errors on code which isn't changed by this branch, all of the form "import foo from '../somewhere/somthing".
It seems if I modify the import path in some way, like, say if it was "../server/foo" but we are already in the server directory, I can change it to "./foo" - which is technically the same directory, then we get past that error. Then another seemingly random import from another file (which used to work), is now failing, it seems the compilation stops on the first broken import & many are broken. I can sweep through many files which should not need to be changed, and seemingly never clear this. Wasp clean / wasp build does not change the outcome.
I believe this is related to a schema change, because had this same scenario ≈ two weeks ago and had to hand-merge-file-by-file until I -finally- got an error message related to schema which I fixed - and this problem went away. I forget what that issue was, but this is the same symptom.
What could be the issue @kapa.ai ?
