-
Notifications
You must be signed in to change notification settings - Fork 61
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
Migration doesn't appear to support prohibitRegexp #145
Comments
We've found this appears to also cause issues if we use C# client to modify content that use the validation. The Client fails and throws a nasty exception. This is becoming a more challenging issue for us. |
|
Hey @wilsondy thanks for following up. Seems like this is a bug in the contentful-migration tool. We will work on adding this validation. Can you please open another ticket with details about what you're experiencing on the .NET sdk here: https://github.com/contentful/contentful.net. Thanks for your patience! |
done... contentful/contentful.net#183 |
This fix has been released as part of contentful-migration v0.19.2 |
Expected Behavior
I should be able to modify content models from the tool even if they contain regex validations.
Actual Behavior
Error message displayed during content migration if a regex is enabled:
"Error: A field can't have "prohibitRegexp" as a validation."
Possible Solution
Steps to Reproduce
Create the following in the UI:
Create a content type migration and attempt to run it.
e.g.
Context
standard content model migration tasks.
Workaround
Manually uncheck prohibit regex and run migration.
I haven't tested any other of the checkboxes, so other errors might be lurking.
Environment
node -v v12.1.0
npm -v 6.9.0
Darwin 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64
The text was updated successfully, but these errors were encountered: