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

Use phpDocumentor #29

Open
sagikazarmark opened this issue Nov 11, 2015 · 6 comments
Open

Use phpDocumentor #29

sagikazarmark opened this issue Nov 11, 2015 · 6 comments
Labels

Comments

@sagikazarmark
Copy link
Member

Do we want to use phpDocumentor?

@mekras raised the idea.

Honestly, I am not sure it is even possible given that the project is separated into several repos, but would be nice to have.

@mekras
Copy link
Contributor

mekras commented Nov 11, 2015

I prefer http://www.apigen.org/.

@sagikazarmark
Copy link
Member Author

Looks great.

@dbu
Copy link
Contributor

dbu commented Nov 11, 2015

myself i use an IDE to develop, so i never look at generated docs. but if somebody wants to set apigen / phpdocumentor up on the website, i have nothing against. i do appreciate good phpdoc on our code, so it can't hurt.

@sagikazarmark
Copy link
Member Author

@mekras how does phpdoc/apigen behave with symfony-like file headers. Actually I decided to remove them as I saw no real added value.

@mekras
Copy link
Contributor

mekras commented Nov 11, 2015

apigen is very tolerant to headers. phpdoc requires both (starting with "/**"), and requires at least summary in each header.

@mekras
Copy link
Contributor

mekras commented Nov 11, 2015

I usually try to write PHPDoc comments following the phpDocumentor rules, because they are well described and more strict. So these comments can be used by various tools, not only by phpdoc/apigen (e. g. IDEs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants