-
Notifications
You must be signed in to change notification settings - Fork 144
Flatten the production code directory structure #230
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
Comments
Sounds good, thanks |
oliverklee
added a commit
to oliverklee/PHP-CSS-Parser
that referenced
this issue
May 30, 2021
This gets the directory structure more in line with what most other projects (including Symfony) are using. (The PHP namespaces are unchanged, though.) Also flatten the directory structure. Fixes MyIntervals#230
oliverklee
added a commit
to oliverklee/PHP-CSS-Parser
that referenced
this issue
Jun 1, 2021
This gets the directory structure more in line with what most other projects (including Symfony) are using. (The PHP namespaces are unchanged, though.) Also flatten the directory structure. Fixes MyIntervals#230
oliverklee
added a commit
to oliverklee/PHP-CSS-Parser
that referenced
this issue
Jun 2, 2021
This gets the directory structure more in line with what most other projects (including Symfony) are using. (The PHP namespaces are unchanged, though.) Also flatten the directory structure. Fixes MyIntervals#230
raxbg
pushed a commit
to raxbg/PHP-CSS-Parser
that referenced
this issue
Sep 15, 2022
This gets the directory structure more in line with what most other projects (including Symfony) are using. (The PHP namespaces are unchanged, though.) Also flatten the directory structure. Fixes MyIntervals#230
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To be more consistent with most other PHP projects, I'd like to change the directory structure like this (without changing the namespaces of the PHP classes):
lib/Sabberworm/CSS/*.php
->src/*.php
@sabberworm @westonruter Would this be okay for you?
The text was updated successfully, but these errors were encountered: