Skip to content
This repository was archived by the owner on Nov 27, 2020. It is now read-only.

Update phpDoc to make it standard compliant #571

Closed
wants to merge 1 commit into from

Conversation

fzaninotto
Copy link
Contributor

PHP Doc stipulates that for @var comments, the type should come first (see http://en.wikipedia.org/wiki/PHPDoc#Tags)

PHP Doc stipulates that for `@var` comments, the type should come first (see http://en.wikipedia.org/wiki/PHPDoc#Tags)
@fabpot
Copy link
Member

fabpot commented Jul 17, 2013

I've no idea what the convention is, but I think it is @var type. So the correct fix would be to remove the $loader part.

@stof
Copy link
Member

stof commented Jul 17, 2013

@fabpot For class properties, the property name should indeed be omitted. But when documenting variables, the name of the variable needs to be used so that tools can know what it is referring to.

@fabpot
Copy link
Member

fabpot commented Jul 17, 2013

@stof, right I read the diff too fast, and didn't realize it was not a class property.

fabpot added a commit that referenced this pull request Jul 22, 2013
This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #571).

Discussion
----------

Update phpDoc to make it standard compliant

PHP Doc stipulates that for `@var` comments, the type should come first (see http://en.wikipedia.org/wiki/PHPDoc#Tags)

Commits
-------

5895afb Update phpDoc to make it standard compliant
@fabpot fabpot closed this Jul 22, 2013
fabpot added a commit that referenced this pull request Sep 6, 2016
This PR was merged into the 2.8 branch.

Discussion
----------

Change inline var PHPDoc syntax

See https://github.com/phpDocumentor/fig-standards/blob/master/proposed/phpdoc.md#722-var

(refer to the [examples](https://github.com/phpDocumentor/fig-standards/blob/master/proposed/phpdoc.md#examples-21))

Related previous PR: #571 (but there was no standard for inline `@var` at the time)

Commits
-------

81ee81a Change inline var PHPDoc syntax
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants