Skip to content
This repository has been archived by the owner on May 16, 2018. It is now read-only.

setCharset is a real method and so the doccomment is not required #698

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bencromwell
Copy link

setCharset is covered by a concrete implementation in the class and not part of the __call magic method.

It therefore doesn't need the @method doccomment declaration.

This change prevents IDEs such as PhpStorm from picking it up as an error.


Have sent in a CLA - I know this is a small change but we have a long-term ZF1 project at work so I anticipate more meaningful PRs in the future!

`setCharset` is covered by a concrete implementation in the class and not part of the __call magic method. 

It therefore doesn't need the @method doccomment declaration.

This change prevents IDEs such as PhpStorm from picking it up as an error.
@froschdesign
Copy link
Member

@bencromwell
Thanks for the PR, but please keep in mind:

Zend Framework version 1 is currently supported in maintenance mode where bug fixes are accepted…

http://framework.zend.com/participate/contributor-guide-v1

You should think about a migration! ZF3 is around the corner and the support of ZF1 will end one day.

@bencromwell
Copy link
Author

@froschdesign thanks for the signposting. Will bear in mind!

I've been slowly refactoring sections but it is a legacy project very tightly coupled in places!

Is EOL expected? The last I saw was something from @weierophinney on Twitter suggesting if the community maintains it it would be able to continue. Apologies if I've got that wrong.

@akrabat
Copy link
Contributor

akrabat commented May 24, 2016

On 24 May 2016, at 09:29, Ben Cromwell [email protected] wrote:

@froschdesign https://github.com/froschdesign thanks for the signposting. Will bear in mind!

I've been slowly refactoring sections but it is a legacy project very tightly coupled in places!

Is EOL expected? The last I saw was something from @weierophinney https://github.com/weierophinney on Twitter suggesting if the community maintains it it would be able to continue. Apologies if I've got that wrong.

I expect that we'll go to security fixes only at some point this year.

@bencromwell
Copy link
Author

@akrabat thanks for the heads up

@froschdesign froschdesign added this to the 1.12.19 milestone May 26, 2016
@froschdesign
Copy link
Member

@froschdesign froschdesign removed this from the 1.12.19 milestone Jul 7, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants