Applying snapshot is a destructive behaviour when you have custom migrations

[hgezim]

Describe the Bug

If you have a custom migration that changes a field type from string (255) to text and it's applied after the snapshot, on container restart, data gets lost as the migration change is reverted.

This follows the guidelines outlined in the docs:

1 npx directus database install
2 npx directus database migrate:latest
3 npx directus schema apply ./path/to/snapshot.yaml
4 mv .custom-migrations/* migrations/
5 npx directus database migrate:latest

To Reproduce

1. Create a collection called Images
2. Create a field called description as type string (255 length)
3. Save the schema and apply it in the order of the docs (above).
4. Create a custom migration to change description type from string to text
5. Create new data for description with > 255 length
6. Restart contianer

Expected:
Snapshot changes not be descrutive.

Actual: snapshot change is destructive and text gets truncated to 255.

Hosting Strategy

Self-Hosted (Docker Image)

[paescuj]

Thanks for opening this issue!
I'm afraid the documentation propagates a wrong way here for the reasons I've explained in #11798 (reply in thread).
Not sure why this has been adopted in the documentation, but I'll see that this part gets adjusted accordingly 👍

[paescuj]

/linear

[github-actions]

🤖 Linear issue created! Maintainers can access it here: ENG-878