Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[WIP] Display friendly content type name in admin#514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
jorrit wants to merge1 commit intoVirtusLab-Open-Source:develop
base:develop
Choose a base branch
Loading
fromjorrit:contenttypedisplayname

Conversation

jorrit
Copy link
Contributor

Also refactors content type name fields in config service

Summary

I noticed that the content type field in the 'add item' dialog shows an 'unfriendly' content type name. I've refactored the code to useinfo.displayName.

TheConfigContentTypeDTO type contained quite a few fields related to the name of the content type:

  • name
  • label
  • labelSingular
  • contentTypeName

There seems to be redundancy between these fields. One of the purposes seems to be to build the GraphQL type name. I've tried to reuse the logic from@strapi/plugin-graphql to do this work instead of doing this in the pluign.

Test Plan

This change is a work in progress and untested. I made these changes as a suggestion. I hope the changes can be tested and refined by the maintainers. Thanks in advance!

SalahAdDin reacted with thumbs up emoji
Also refactors content type name fields in config service
@cyp3riuscyp3rius changed the base branch frommaster todevelopJanuary 27, 2025 21:10
@SalahAdDin
Copy link
Contributor

@jorrit man?

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@cyp3riuscyp3riuscyp3rius approved these changes

Assignees

@CodeVoyagerCodeVoyager

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@jorrit@SalahAdDin@cyp3rius@CodeVoyager

[8]ページ先頭

©2009-2025 Movatter.jp