You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
How should potential broken links be handled? So let Content Type A the target for deletion, and Content Type B a content type with a link field that might be tied to Content Type A entries.
Should one param for the exposed method be filter?
Should this be a 2 confirmations step method`? First execution would be a dry run search of entries with a potential
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: