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
59e14fabb4
[Issue-5772] Add sort feature on settings tables ( #5787 )
...
## Proposed Changes
- Introduce a new custom hook - useTableSort to sort table content
- Add test cases for the new custom hook
- Integrate useTableSort hook on to the table in settings object and
settings object field pages
## Related Issue
https://github.com/twentyhq/twenty/issues/5772
## Evidence
https://github.com/twentyhq/twenty/assets/87609792/8be456ce-2fa5-44ec-8bbd-70fb6c8fdb30
## Evidence after addressing review comments
https://github.com/twentyhq/twenty/assets/87609792/c267e3da-72f9-4c0e-8c94-a38122d6395e
## Further comments
Apologies for the large PR. Looking forward for the review
---------
Co-authored-by: Félix Malfait <felix.malfait@gmail.com >
Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com >
2024-08-14 17:11:17 +02:00
63387424c3
Fix transliteration for metadata + transliterate select options ( #5430 )
...
## Context
Fixes #5403
Transliteration is now integrated to form validation through the schema.
While it does not impede inputting an invalid value, it impedes
submitting a form that will fail as the transliteration is not possible.
Until then we were only performing the transliteration at save time in
the front-end, but it's best to provide the information as soon as
possible. Later we will add helpers to guide the user (eg "This name is
not valid": https://github.com/twentyhq/twenty/issues/5428 ).
---------
Co-authored-by: Charles Bochet <charles@twenty.com >
2024-05-15 21:43:58 +02:00
ff39ba5a15
[fix] Support non latin characters in schema names ( #5063 )
...
Fixes #4943
## How was it tested?
Local (front + /metadata)
Unit tests for utils
---------
Co-authored-by: Weiko <corentin@twenty.com >
2024-04-23 13:37:29 +02:00
