2fc300a63c
Remove number from label identifier list ( #12831 )
2025-06-24 18:05:27 +00:00
d51a797d91
Replace shouldSyncNameAndLabel with isLabelSyncedWithName ( #8067 )
...
For consistency.
This was not deployed yet so allowing myself just to rename everything,
meaning developers will need to reset their db.
2024-10-25 18:28:58 +02:00
bf2ba25a6e
Add shortcut metadata to data models & CommandMenu ( #7977 )
...
Resolves https://github.com/twentyhq/twenty/issues/7503
---------
Co-authored-by: Félix Malfait <felix@twenty.com >
2024-10-25 11:38:30 +02:00
414f2ac498
Support custom object renaming ( #7504 )
...
This PR was created by [GitStart](https://gitstart.com/ ) to address the
requirements from this ticket:
[TWNTY-5491](https://clients.gitstart.com/twenty/5449/tickets/TWNTY-5491 ).
This ticket was imported from:
[TWNTY-5491](https://github.com/twentyhq/twenty/issues/5491 )
---
### Description
**How To Test:**\
1. Reset db using `npx nx database:reset twenty-server` on this PR
1. Run both backend and frontend
2. Navigate to `settings/data-model/objects/ `page
3. Select a `Custom `object from the list or create a new `Custom
`object
4. Navigate to custom object details page and click on edit button
5. Finally edit the object details.
**Issues and bugs**
The Typecheck is failing but we could not see this error locally
There is a bug after updating the label of a custom object. View title
is not updated till refreshing the page. We could not find a consistent
way to update this, should we reload the page after editing an object?
###
Demo
<https://www.loom.com/share/64ecb57efad7498d99085cb11480b5dd?sid=28d0868c-e54f-454d-8432-3f789be9e2b7 >
### Refs
#5491
---------
Co-authored-by: gitstart-twenty <gitstart-twenty@users.noreply.github.com >
Co-authored-by: gitstart-twenty <140154534+gitstart-twenty@users.noreply.github.com >
Co-authored-by: Marie Stoppa <marie.stoppa@essec.edu >
Co-authored-by: Charles Bochet <charles@twenty.com >
Co-authored-by: Weiko <corentin@twenty.com >
2024-10-24 11:52:30 +00:00
7c3e82870c
[fix] Increment cache version after object/field/relation update ( #5316 )
...
Fixes #5276 .
Updates were not triggering a cache version incrementation because they
do not trigger migrations while that is where the caching version logic
was.
We have decided to move the cache incrementation logic to the services.
2024-05-07 16:30:25 +02:00
e5c1309e8c
feat: wip server folder structure ( #4573 )
...
* feat: wip server folder structure
* fix: merge
* fix: wrong merge
* fix: remove unused file
* fix: comment
* fix: lint
* fix: merge
* fix: remove console.log
* fix: metadata graphql arguments broken
2024-03-20 16:23:46 +01:00
