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

Document how to create a custom type guesser#3597

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

Merged
weaverryan merged 3 commits intosymfony:2.3fromwouterj:issue_481
Mar 9, 2014

Conversation

wouterj
Copy link
Member

QA
Doc fix?no
New docs?yes
Applies toall
Fixed tickets#481

* :method:`Symfony\\Component\\Form\\FormTypeGuesserInterface::guessMaxLength` -
tries to guess the value of the ``max_length`` option;
* :method:`Symfony\\Component\\Form\\FormTypeGuesserInterface::guessPattern` -
tries to guess the value of the ``pattern`` option.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

we could link the option to their descriptions in the reference docs

@xabbuh
Copy link
Member

👍 Great work! But I am wondering if this article should be moved to the cookbook.

@wouterj
Copy link
MemberAuthor

But I am wondering if this article should be moved to the cookbook.

It's independent of the framework and very usefull if you are using the form component standalone.

@xabbuh
Copy link
Member

It's independent of the framework and very usefull if you are using the form component standalone.

Actually, this also applies to a lot of cookbook articles, doesn't it?

@wouterj
Copy link
MemberAuthor

this also applies to a lot of cookbook articles, doesn't it?

Only a few are fully framework independant and I really want to move them to the components section

---------------------

In this section, you are going to build a PHPDoc type guesser. At first, you
need to create a class which extends

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

wich implements

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

+1

AND, how about we change the header to "Create a PHPDoc Type Guesser" and then remove the first sentence (or replace it with something describing what this means - e.g. "In this section, you are going to build a guesser that reads information about fields from the PHPDoc above the properties").

@wouterj
Copy link
MemberAuthor

Thank you,@weaverryan@xabbuh@ggam. I've fixed all of your comments.

@weaverryan
Copy link
Member

Awesome! So many new pieces coming into the docs lately - thanks!

weaverryan added a commit that referenced this pull requestMar 9, 2014
This PR was merged into the 2.3 branch.Discussion----------Document how to create a custom type guesser| Q   | A| --- | ---| Doc fix? | no| New docs? | yes| Applies to | all| Fixed tickets |#481Commits-------0d37a3b Applied comments3b3cd6f Added referencesf36fdb7 Documented FormTypeGuesserInterface
@weaverryanweaverryan merged commit0d37a3b intosymfony:2.3Mar 9, 2014
@wouterjwouterj deleted the issue_481 branchMarch 9, 2014 22:04
@wouterj
Copy link
MemberAuthor

@weaverryan yeah, I decided it was time to clear up the milestones. My goal is to have all milestoned issues at least tagged with "has pr" when 2.5 is released.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@wouterj@xabbuh@weaverryan@ggam

[8]ページ先頭

©2009-2025 Movatter.jp