maoberlehner / storyblok-migrate

Storyblok schema migrations
MIT License
30 stars 7 forks source link

storyblok-migrate doesn't work without using the parameter --components #2

Open AnasBoulmane opened 5 years ago

AnasBoulmane commented 5 years ago

Current behavior

storyblok-migrate doesn't work without using the parameters --component-migrations --components

Expected behavior

be able to migrate components using the guided UI mode.

Environment

node --version: v10.15.3 storyblok-migrate: ^0.3.1

Minimal reproduction of the problem with instructions

change the schema of test.js:

image

Running component migrations:

 $ npx storyblok-migrate
✔ Do you want to run component migrations? · No / Yes
✔ Migrate all components? · No / Yes
✔ Do you want to run content migrations? · No / Yes
✔ Migrate all content types? · No / Yes
 $ npx storyblok-migrate
✔ Do you want to run component migrations? · No / Yes
✔ Migrate all components? · No / Yes
✔ Which components do you want to migrate? · Test has been updated
✔ Do you want to run content migrations? · No / Yes
✔ Migrate all content types? · No / Yes

the previous commands are executed without updating the test component. but that work using --component-migrations --components parameters.

 $ npx storyblok-migrate --component-migrations --components test
Test has been updated component has been updated
maoberlehner commented 5 years ago

Thanks again for the detailed bug report.

Unfortunately I can't reproduce right now. But I've seen you're using windows in your other issue so it might me some issue with directory paths or something like that. I'll take a closer look as soon as a I'm able to shift some time to this.

Thx!

maoberlehner commented 5 years ago

There is one question missing in the snippet you posted:

✔ Ready to start migration? · No / Yes

Did you just not copy that line or were you not asked this question?

AnasBoulmane commented 5 years ago

I am not asked this question. and I'm using Mac OS.

maoberlehner commented 5 years ago

I am not asked this question.

That's strange 🤔

and I'm using Mac OS.

Oh my bad, sorry!

maoberlehner commented 5 years ago

@AnasBoulmane do you have set your display_name fields? I've noticed that setting them to an empty string for example leads to a similar error.

AnasBoulmane commented 5 years ago

hi @maoberlehner, I set the display_name to Test has been updated image