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

Bugfix Library #152

Merged
merged 2 commits into from
Feb 12, 2016
Merged

Bugfix Library #152

merged 2 commits into from
Feb 12, 2016

Conversation

nyamsprod
Copy link
Member

- bug fix stream filter #72
- improve public API by deprecating (get|set)EncodingFrom
@@ -190,7 +190,7 @@ protected function newInstance($class, $open_mode)
$csv->delimiter = $this->delimiter;
$csv->enclosure = $this->enclosure;
$csv->escape = $this->escape;
$csv->encodingFrom = $this->encodingFrom;
$csv->input_encoding = $this->input_encoding;
Copy link
Contributor

Choose a reason for hiding this comment

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

just curious: why snake_case instead of camelCase?

Copy link
Member Author

Choose a reason for hiding this comment

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

I was in the mood for snake case :) . Seriously I did this to match $input_bom and $output_bom which are already in snake case. I should probably review all the codebase and make a clear decision between both coding style. Of note none of them are in contradiction to PSR2 if I recall but yes the code needs consistency.

I'll will check the codebase for consistency in property name after this PR is merge

Copy link
Contributor

Choose a reason for hiding this comment

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

I was in the mood for snake case

😄

none of them are in contradiction to PSR2

You're right

nyamsprod added a commit that referenced this pull request Feb 12, 2016
@nyamsprod nyamsprod merged commit 8f18dde into master Feb 12, 2016
*
* DEPRECATION WARNING! This method will be removed in the next major point release
*
* @deprecated deprecated since version 4.1
Copy link
Contributor

Choose a reason for hiding this comment

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

since version 4.1? should be 8.x.x (to be released)

Copy link
Contributor

Choose a reason for hiding this comment

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

It's deprecated sinde 4.1, and will be removed in the next major version.

Copy link
Contributor

@vlakoff vlakoff May 3, 2016

Choose a reason for hiding this comment

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

I thought of some typo / old PR. Okay then, I trust you :)

@nyamsprod
Copy link
Member Author

@vlakoff indeed you are correct it is a typo and the deprecation message was changed in the master. 👍

I should point out that I had a hard time finding this discussion since the comment was made on an already closed PR

@nyamsprod nyamsprod deleted the bugfix/streamfilter branch May 23, 2016 08:10
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.

3 participants