in development only: migrate-save description cannot contain space about wasp HOT 4 CLOSED

I am experiencing the same problem on Linux! Although I feel like sometimes it worked, lately it does not seem to work hm. I wonder if even prisma migrate-save allows spaces? Or is this a mistake on our side?

How to go about this: First, check how prisma migrate-save works, if they allow space in the migration name. If not, that is it, we will also not allow it. If they do allow it, figure out why we don't -> are we incorrectly passing the arg(uments) to prisma migrate-save? Maybe we need to wrap them in ""? Just guessing.

from wasp.

Tried to reproduce again, but couldn't, seems it is working now. Prisma is allowing spaces.

I also checked out the implementation and that also looks ok - proc from System.Process accepts a list of arguments and getArgs from System.Environment parses e.g. "Add user" into ["Add user"] -> removes the quotes but keeps it as one string. So I believe that proc which accepts a [String] of args knows how to handle a string with spaces.

from wasp.

Managed to reproduce it: happens only in development, when running e.g. ./run wasp db migrate-save "some name". Investigate further, try with stack exec instead of run.

from wasp.

We deprecated migrate-save, now it is migrate-dev and name is asked for interactively.

from wasp.