464a480043
Continue ESLINT9 Migration ( #13795 )
...
Might already fix #13793
2025-08-10 23:25:58 +02:00
5fae14377a
Eslint migration 4 ( #13773 )
...
A new attempt to migrate!
2025-08-08 16:21:57 +02:00
8b4b9ef8da
Change type import rule ( #13751 )
...
Forcing "type" to be explicit, works best will rollup on the frontend to
exclude depdendencies
2025-08-08 01:27:05 +02:00
cc29c25176
feat: new relation sync-metadata, twenty-orm, create/update ( #10217 )
...
Fix
https://github.com/twentyhq/core-team-issues/issues/330#issue-2827026606
and
https://github.com/twentyhq/core-team-issues/issues/327#issue-2827001814
What this PR does when `isNewRelationEnabled` is set to `true`:
- [x] Drop the creation of the foreign key as a `FieldMetadata`
- [x] Stop creating `RelationMetadata`
- [x] Properly fill `FieldMetadata` of type `RELATION` during the sync
command
- [x] Use new relation settings in TwentyORM
- [x] Properly create `FieldMetadata` relations when we create a new
object
- [x] Handle `database:reset` with new relations
---------
Co-authored-by: Charles Bochet <charles@twenty.com >
Co-authored-by: Charles Bochet <charlesBochet@users.noreply.github.com >
2025-04-22 19:01:39 +02:00
f0383e3147
feat: twenty orm sync ( #5266 )
...
This PR is updating all object metadata entities with the new
decorators, and deleting the old ones.
This way we can use the new TwentyORM with all the standard objects.
---------
Co-authored-by: Weiko <corentin@twenty.com >
2024-05-15 16:58:47 +02:00
Félix Malfait