Skip to content
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

non-camel-case variable code conventions (with extra tests) #57

Merged
merged 6 commits into from
Mar 27, 2016
Merged

non-camel-case variable code conventions (with extra tests) #57

merged 6 commits into from
Mar 27, 2016

Conversation

linaori
Copy link

@linaori linaori commented May 13, 2015

Because people keep running into issues with collections and $underscore_properties , I have added extra tests on the changes of #29 to to prove that it's backwards compatible. It seems like that one won't be merged because the test cases are missing.

This PR includes the exact same changes as #29 but with 3 extra tests.

@linaori linaori changed the title Feature/collection get is non-camel-case variable code conventions (with extra tests) May 13, 2015
@linaori
Copy link
Author

linaori commented May 13, 2015

Failing tests are only on hhvm-nightly, which is not supported anymore according to the error message.

@@ -45,12 +45,10 @@ public static function getObjectFieldValue($object, $field)
if (is_array($object)) {
return $object[$field];
}

Copy link
Member

Choose a reason for hiding this comment

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

please don't remove these empty lines

Copy link
Author

Choose a reason for hiding this comment

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

Ah my bad, I was debugging a bit in a particular test case, I will revert this on Monday.

@stof
Copy link
Member

stof commented May 13, 2015

the HHVM-nightly builds are now removed

@TomasVotruba
Copy link

What needs to be done here?

@linaori
Copy link
Author

linaori commented Mar 21, 2016

I actually forgot to provide the last patch, which is added now.

@Ocramius is there anything this PR is still missing in order to get the fix through?

@mikeSimonson
Copy link
Contributor

@iltar Baswed on the discution on #29 I am going to consider that this implement the desired behaviour.

@linaori
Copy link
Author

linaori commented Mar 27, 2016

@mikeSimonson You have our thanks!

@yannickl88
Copy link
Contributor

@mikeSimonson Do you have some info when there will be a release that includes this pull?

@mikeSimonson
Copy link
Contributor

I need to fix a few stuff that I pulled here before to release. I am not making any promise but I hope soon.

@yannickl88
Copy link
Contributor

okay cool! looking forward to it

@maresja1
Copy link

This is not enough. Suppose my field is called isCompany, as it is bool and name company would suggest a reference to a company. I really don't want to call the getter method for it isIsCompany or getIsCompany - I consider that as ugly. Why can't I call the getter same as the field. I suggest adding possibility for users of Doctrine to override the naming convention, or at least consider naming standard where getters are called the same as the fields.

@yannickl88
Copy link
Contributor

@maresja1 What you are suggesting would be a great addition. However, this would require an extension point for the ClosureExpressionVisitor. I would recommend creating a new Issue since this one is already merged.

@mikeSimonson mikeSimonson self-assigned this Feb 11, 2017
@mikeSimonson mikeSimonson added this to the 1.4.0 milestone Feb 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants