-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
#[CoversNamespace]
and #[UsesNamespace]
#4463
Labels
feature/code-coverage
Issues related to code coverage (but not php-code-coverage)
feature/metadata
Issues related to attributes and annotations
type/enhancement
A new idea that should be implemented
Comments
sebastianbergmann
added
type/enhancement
A new idea that should be implemented
feature/code-coverage
Issues related to code coverage (but not php-code-coverage)
labels
Sep 23, 2020
sebastianbergmann
added
the
feature/metadata
Issues related to attributes and annotations
label
Jun 3, 2021
sebastianbergmann
changed the title
@covers / @uses annotations for namespaces
Mar 10, 2024
#[CoversNamespace]
and #[UsesNamespace]
@spriebsch Do you still think that this would be useful? |
I'd say this conversation is way beyond what should be discussed in ticket comments. |
Hi! I'd be interested into this feature. Would you accept a PR about it? |
I do not see how this can be implemented before sebastianbergmann/php-code-coverage#519 has been implemented. |
this issue is pretty old, is there a blocker here? or does it needs a huge effort to be fixed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/code-coverage
Issues related to code coverage (but not php-code-coverage)
feature/metadata
Issues related to attributes and annotations
type/enhancement
A new idea that should be implemented
Suggested by @spriebsch:
@covers-namespace vendor\foo
should cover all units of code where the fully qualified name of the unit begins withvendor\foo
@uses-namespace vendor\foo
should allow all units of code where the fully qualified name of the unit begins withvendor\foo
The text was updated successfully, but these errors were encountered: