-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New best-practice for Symfony Forms #5077
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
actionable
Clear and specific issues ready for anyone to take them.
good first issue
Ideal for your first contribution! (some Symfony experience may be required)
Comments
Same question as in #5076: Should we use Besides that I like this idea. 👍 |
@xabbuh dots are forbidden in type names, so the answer is no |
👍 |
weaverryan
added a commit
that referenced
this issue
Mar 24, 2015
…(javiereguiluz) This PR was merged into the 2.3 branch. Discussion ---------- Added a new best practices for custom form field types | Q | A | ------------- | --- | Doc fix? | no | New docs? | yes | Applies to | all | Fixed tickets | #5077 Commits ------- 0696daf Fixed errors, typos and grammar issues. (I managed to fail at everything!) 8eb1240 Added a new best practices for custom form field types
I've just merged this in and updated the description to have a todo to add the |
Part B is done so this can be closed, right? |
You are right @snoek09. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
actionable
Clear and specific issues ready for anyone to take them.
good first issue
Ideal for your first contribution! (some Symfony experience may be required)
In #5076 we've reworded an important note as follows:
Should we make the
app_
prefix recommendation a formal best practice?app_
prefixThe text was updated successfully, but these errors were encountered: