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

Support @psalm-internal #738

Open
weirdan opened this issue Feb 23, 2023 · 2 comments
Open

Support @psalm-internal #738

weirdan opened this issue Feb 23, 2023 · 2 comments

Comments

@weirdan
Copy link
Contributor

weirdan commented Feb 23, 2023

BCC supports @internal docblock tag that can be used to limit access to the top-level namespace (at least, that's how Psalm interprets it).

Psalm also supports @psalm-internal tag that allows you to grant access in a more modular fashion (you can reference sub-namespaces, classes, and even individual methods and functions), but BCC ignores that tag.

@Ocramius
Copy link
Member

Analysis of various symbols is context-less, so a @psalm-internal \Some\Namespace would be equivalent to @internal for this tool: is that sufficient?

@weirdan
Copy link
Contributor Author

weirdan commented Feb 23, 2023

I think that would be sufficient, it's better than nothing, for sure.

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

No branches or pull requests

2 participants