Adds theme namespaces to the "containers.namespaces" and "class_loader"
services. This allows themes to define classes and have discoverable annotated
plugin definitions.
Theme namespaces are added with the pattern Drupal\Theme\<theme name> to
keep theme namespaces differentiated from the standard Drupal module namespaces
Drupal\<module name>.
Module also includes plugin definition and discovery classes to assist with creating
plugins that can be loaded based on the active theme.
Project link
https://www.drupal.org/project/themespace
Git instructions
git clone --branch '1.0.x' https://git.drupalcode.org/project/themespace.git
Comments
Comment #2
lemming commentedComment #3
avpadernoThank you for applying! Reviewers will review the project files, describing what needs to be changed.
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smother review.
To reviewers: Please read How to review security advisory coverage applications, What to cover in an application review, and Drupal.org security advisory coverage application workflow.
Comment #4
andrei.vesterliHello @lemming
I've tested your module and it does a great job!
The only 2 things I see are:
1. Please, adjust the composer.json according to this documentation.
2. I've ran the tests via command:
php scripts/run-tests.sh themespace(from the core folder) and got this:my stack:
core: 9.3.12
PHP: 8.0
PHPUnit: 9.5.20
drupal-dev: 9.3.x
simpletest-simpletest: 3.x-dev@dev
phpspec/prophecy-phpunit: ^2.
anyway, some of the classes seem to be as not found. Probably, I miss something but this is what I have.
Regards,
Andrei
Comment #5
andrei.vesterliComment #6
lemming commented@andrei.vesterli thanks for reviewing.
I appreciate the thoughtful review and keeping the community growing.
Comment #7
andrei.vesterli@lemming
Hmm, it seems to be much better! Thx for the fast feedback!
A would suggest you use the automated testing section for your project page once you have these tests. Also, run them in the dev branch and configure them to run weekly. This is really good to have once you'll get some development stuff done or something new merged.
Regards,
Andrei
Comment #8
lemming commentedComment #9
lemming commentedUpdated the repository default branch and the Git instructions to use the "1.0.x" branch.
Comment #10
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.