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

Clarify difference between /public and /src #36

Open
fulldecent opened this issue Jul 7, 2017 · 4 comments
Open

Clarify difference between /public and /src #36

fulldecent opened this issue Jul 7, 2017 · 4 comments

Comments

@fulldecent
Copy link

Please clarify the difference between /public and /src.

A common setup is to use one index.php file to route requests to other parts of the project. Please address this setup specifically in the documentation.

@pmjones
Copy link

pmjones commented Jul 14, 2017

What parts of the phrasing do you feel need clarification?

@fulldecent
Copy link
Author

Maybe I am reading it wrong, but extra information could be included such as:

If the package provides a root-level directory for web server files (e.g. index.php), it MUST be named public/.

If the package provides a root-level directory for PHP source code files (e.g. class definitions), it MUST be named src/.

@fulldecent
Copy link
Author

Would a PR that fixes this be in scope to be merged?

@iio7
Copy link

iio7 commented Feb 29, 2020

Why in the world would you call the directory "src"? It makes no sense what so ever! There is no source code what so ever. There is PHP application code, which has nothing to do with source code.

Class definitions are classes, why not just call it what it is, "classes". There is no need to get clever about it.

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

No branches or pull requests

3 participants