felixjung / contentful-utils Goto Github PK

Hey hey,

cool stuff, you're doing here. I spotted a mistake in the readme though.

https://github.com/felixjung/contentful-utils#deleting-fields

Looks like a copy and paste mistake. :)

I would fix it myself but I'm not sure how the command works ( https://github.com/felixjung/contentful-utils#delete-fields-options doesn't explain well enough I guess)

Thanks and keep it going.

Somehow publishing after overwriting fields does not work.

Should allow to copy all entries of a content type from one space to another.

As @stefanjudis pointed out, the README could use some love. One thing that bothers me is that global command options are missing in the help output for sub-commands.

We could have a command to duplicate a field under a different name. This is currently not available in the UI.

Sometimes you might want to copy/duplicate an existing content type (across spaces).

When selectively migrating spaces (i.e. not just cloning a space), it would be beneficial to selectively copy content types, and individual fields from one space to another. We should also be able to do so in a forceful manor.

Clean up some things.

• Put any logging messages, if they are still needed, into some log hash and fetch them from there. Removes distractions from code.
• Are there cleaner ways to split the whole CLI config of yargs up? Maybe move to the respective commands?
• Move to lodash/fp.
• Think about moving some functions around.
• Fix whatever you find.

• lint:watch
• unit:watch

I do remember config files not working as expected with yargs. Should be fixed. Than you can have a folder of space config files and reuse them.

Would be handy to be able to delete all entities of a given type at once.

Now that we have such a nice Ava setup, we should start writing tests.

contentful-export is using listr to create nice tasks lists while running a command. Would totally be an option here.

Dealing with all that async Contentful code is messy. Would be cool to use is as grounds for experimenting with async/await.

Sometimes to update the configuration of a field, for example the validation. If other content types are using the "same" field, it would be useful to copy the potentially improved configuration over, provided it is compatible.