-
Notifications
You must be signed in to change notification settings - Fork 150
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
[Suggestion]: Delete entries #1388
Comments
Hello, @neptunus, in the past I've thought about this too. My rationale is mostly required or ideal preconditions before running migration. I've also run simply test or experimental migration scripts and I've wanted to start from scratch. Some open questions
Technical considerations
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
See #852 — when we use the migration API to clean up the content model and delete deprecated fields, we're missing the ability to delete entries of that field type at the same time.
Possible Solution
I would be fine with this being an option that could be passed to the
deleteContentType
method (as suggested in the previous ticket) or if this would be added as a standalone method.deleteEntriesOfType(id: string)
or something along those lines.Context
The problem lies in having to go in and manually delete entries in the GUI (on the master environment no less) before running migrations, which is a step out of the process we have in place.
The text was updated successfully, but these errors were encountered: