Describe the bug
In case an alias (e.g a group) has the same name/key as a field, one of them is missed in the sync and the other one deleted on push without any notification.
To Reproduce
Create a group Content and a field content (haven't tested if the casing actually makes a difference)
Run directus-sync pull
Open JSON file snapshots/fields/<collection_name>/content.json
Only the actual field OR the alias are tracked
Run directus-sync push and the untracked one (field or alias) is deleted
Expected behavior
As directus aliasses aren't real database fields, both can have the same name / key. Not sure how the extension could handle this, but maybe alias fields could get a prefix in the filename.
Versions (please complete the following information):
Describe the bug In case an alias (e.g a group) has the same name/key as a field, one of them is missed in the sync and the other one deleted on push without any notification.
To Reproduce
Contentand a fieldcontent(haven't tested if the casing actually makes a difference)directus-sync pullsnapshots/fields/<collection_name>/content.jsondirectus-sync pushand the untracked one (field or alias) is deletedExpected behavior As directus aliasses aren't real database fields, both can have the same name / key. Not sure how the extension could handle this, but maybe alias fields could get a prefix in the filename.
Versions (please complete the following information):