mirror of
https://github.com/twentyhq/twenty.git
synced 2024-12-28 23:03:41 +03:00
a374922902
## Context An object should always have a labelIdentifier (would be its primary key at least). If the associated field is deleted by a user, it will break the app. Ideally we should handle that on the DB level but we don't have a FK for this column yet. In the meantime I'm adding the validation check in the backend, note that this is already handle on the FE side since the "archive/delete" buttons don't appear for such fields so you need to reassign it to another field first which is the desired behaviour. |
||
|---|---|---|
| .. | ||
| twenty-chrome-extension | ||
| twenty-docker | ||
| twenty-emails | ||
| twenty-front | ||
| twenty-postgres | ||
| twenty-server | ||
| twenty-ui | ||
| twenty-utils | ||
| twenty-website | ||
| twenty-zapier | ||