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

Add documentation for enum property.rst#20887

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

Closed
cadot-eu wants to merge2 commits intosymfony:7.2fromcadot-eu:patch-1

Conversation

cadot-eu
Copy link
Contributor

A note and an example class for the enum type which has an undocumented peculiarity on the path to give

A note and an example class for the enum type which has an undocumented peculiarity on the path to give
@xabbuh
Copy link
Member

I am not sure I understand what this is trying to clarify. Can you elaborate a bit on your idea?

@cadot-eu
Copy link
ContributorAuthor

When adding an enum type property, you must put a path and not just the name of the entity as for relationships for example.

patchsCo-authored-by: Oskar Stark <oskarstark@googlemail.com>
@OskarStark
Copy link
Contributor

I also don't get it. Thanks for proposing, feel free to explain and reopen this issue.

@cadot-eu
Copy link
ContributorAuthor

cadot-eu commentedJul 2, 2025
edited by OskarStark
Loading

I also don't get it. Thanks for proposing, feel free to explain and reopen this issue.

When we create an entity and we want to add an enum type we have no indication that gives an example to add the path while for other types like relationships it asks for the type and there is no need to give the path. This particularity is not documented and for beginners, we can tend to put just State for example instead of putting the complete path without php. Otherwise, perhaps it would be good to impose the path as /app/Entity/Enums and in this case we could search and list the available Enums.
What do you think? Am I clearer?

@xabbuh
Copy link
Member

I am sorry, but I still don't understand. Where in the Doctrine context do you have to add a path?

@cadot-eu
Copy link
ContributorAuthor

php bin/console m:e test
New property name (press to stop adding fields):
enumtest
Field type (enter ? to see all types) [string]:
enum
Enum class:
I type not a name but path with name App\Entity\Enums\state not state or state.php
It's not documented and a difficult for newbies

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

@OskarStarkOskarStarkOskarStark left review comments

Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@cadot-eu@xabbuh@OskarStark@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp