Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Code style standardization on form type options#4967
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
70a4484 toc06967cComparec06967c tob37314bComparewouterj commentedFeb 6, 2015
mimol91 commentedFeb 7, 2015
wouterj commentedFeb 7, 2015
Yes, that's fine by me |
mimol91 commentedJun 6, 2015
@wouterj |
xabbuh commentedJun 6, 2015
👍 looks great |
wouterj commentedJun 7, 2015
Hi@mimol91! Thanks for your work and taking care of updating this PR. Something still went wrong while trying to merge it, so I started a new branch and cherry-picked you commit. This resulted in a new PR:#5365 (you're still the author of the commit). I'll merge that PR, so I'll close this PR. Thanks again! |
mimol91 commentedJun 7, 2015
@wouterj |
I m not quite sure how to set proper name for bool attributes.
I read on SF Code standards "For type-hinting in PHPDocs and casting, use bool (instead of boolean or Boolean)", however I change it to boolean. (Most commonly used)