[REFACTOR][FRONT]: Remove objectMetadata and fieldMetadata sluggification (#9441)
# Introduction For motivations and context please have a look to https://github.com/twentyhq/twenty/pull/9394 whom this PR results from. In this pull-request we remove any `metadataField` and `objectMetadata` sluggification. We directly consume `objectMetadata.namePlural` and `metadataField.name`, ***it seems like that historically the consumed `metadataField.name`*** are we sure that we wanna change this behavior ? ## Notes Unless I'm mistaken by reverting the `kebabcase` url formatting we might be creating deadlinks that user could have save beforehand => Discussed with Charles said it's controlled risk. --------- Co-authored-by: Paul Rastoin <paulrastoin@Pauls-MacBook-Pro.local>
This commit is contained in:
@ -35,7 +35,7 @@ export const ObjectOptionsDropdownHiddenFieldsContent = () => {
|
||||
});
|
||||
|
||||
const settingsUrl = getSettingsPagePath(SettingsPath.ObjectDetail, {
|
||||
objectSlug: objectNamePlural,
|
||||
objectNamePlural,
|
||||
});
|
||||
|
||||
const { handleColumnVisibilityChange, hiddenTableColumns } =
|
||||
|
||||
@ -54,8 +54,8 @@ export const ObjectOptionsDropdownHiddenRecordGroupsContent = () => {
|
||||
const viewGroupSettingsUrl = getSettingsPagePath(
|
||||
SettingsPath.ObjectFieldEdit,
|
||||
{
|
||||
objectSlug: objectNamePlural,
|
||||
fieldSlug: recordGroupFieldMetadata?.name ?? '',
|
||||
objectNamePlural,
|
||||
fieldName: recordGroupFieldMetadata?.name ?? '',
|
||||
},
|
||||
);
|
||||
|
||||
|
||||
@ -69,7 +69,7 @@ export const ObjectOptionsDropdownRecordGroupFieldsContent = () => {
|
||||
const newSelectFieldSettingsUrl = getSettingsPagePath(
|
||||
SettingsPath.ObjectNewFieldConfigure,
|
||||
{
|
||||
objectSlug: objectNamePlural,
|
||||
objectNamePlural,
|
||||
},
|
||||
{
|
||||
fieldType: FieldMetadataType.Select,
|
||||
|
||||
Reference in New Issue
Block a user