-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provided schema doesn't exist for path with space in name #5450
Comments
@DevanB Thanks for the write up! I can reproduce this. And I think I've narrowed it down to the change I made here: #5147. The debugger shows the problem pretty clearly: I made the change to fix this issue: #5135. Would you be up for trying to fix this one now that we think we know where things are going wrong? |
Could we make sure there’s a unit test for this when the fix is in place please? |
For posterity sake I am sharing the forum post I created when I ran into this same issue here Replacing the space in the folder name with an underscore |
@DevanB @Isaac-Tait this is now patched in v1.3.3: https://github.com/redwoodjs/redwood/releases/tag/v1.3.3. |
Hi there! Sometime recently I upgraded from 1.1 to 1.3. After doing this (painlessly), I noticed an error when I would run
yarn rw prisma migrate dev
in the form of:Error: Provided --schema at /Users/devanb/My doesn't exist.
The full error can be seen here
Since the initial time I got the error, I had changed my parent folder to not have a space within it and went on my way. However, over the last few days, I've seen others recording this issue on Discord as well. So I decided to create this quick walk-through to create a minimal reproduction:
mkdir -p My\ Apps && cd My\ Apps
yarn create redwood-app my-rw-app --typescript
cd my-rw-app
yarn rw prisma migrate dev
Assuming all goes as (unfortunately) planned, you should be presented with an error very similar to the one at the beginning of this post (within the details accordion).
I'll be glad to assist as much as possible, but wouldn't know where to begin to debug this issue.
The text was updated successfully, but these errors were encountered: