import --no-update option doesn't work about contentful-cli HOT 8 CLOSED

@Khaledgarbaya Any reason not to just embrace the yargs convention? All you have to do is change it from 'no-update' to 'update' and flip the default from false to true.

from contentful-cli.

I think I know why... it seems this option is not implemented in https://github.com/contentful/contentful-import/blob/master/lib/parseOptions.js

from contentful-cli.

Confirmed that this is still a bug in 0.16.0 on macOS. It looks like the yargs argument is named no-update (see: https://github.com/contentful/contentful-cli/blob/master/lib/cmds/space_cmds/import.js#L53). By convention yargs uses the no- prefix as a way to flip a boolean flag. So it's interpreting --no-update as --update false (or whatever the flag value for false is) and bombing out because there is no update option. 🙄

If you change .option('no-update', { to .option('update', { it stops bombing out. However it still appears to update (assets, at least).

from contentful-cli.

@chrislambe thank you for these helpful details. We will have a look!

from contentful-cli.

we can maybe change it to prevent-update

from contentful-cli.

Also experincing trouble with this.

Also, I want to use it to prevent assets from updating, so even with the "fix" suggested by @chrislambe it's no use to me.

from contentful-cli.

Please follow on #118.

from contentful-cli.

🎉 This issue has been resolved in version 0.33.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from contentful-cli.