We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given the class example at https://psalm.dev/docs/annotating_code/typing_in_psalm/#specifying-stringint-options-aka-enums
it's common to have a list of enum values, that belong together. Usually a list of possible statuses, e.g.
class Subject { const STATUS_OK = 0; const STATUS_KO = 1; }
Listing all possible statuses would be boring, as such i suggest
@param Subject::STATUS_* $status
Additionally it could allow any const using Subject::* $status, but it looks less like a known const type :/ so it could be confusing to reason about.
Subject::* $status
The text was updated successfully, but these errors were encountered:
Create a PR for the documentation and I'll add the implementation
Sorry, something went wrong.
@param A::SOME_*|A::SOME_X should be marked redundant btw. Nice to have i guess :)
@param A::SOME_*|A::SOME_X
@param A::SOME_*|A::SOME_X should be marked redundant
I won't bother with that, I don't think
I had a perfect use-case for * today:
*
/** * @psalm-type _LogLevel=LogLevel::EMERGENCY|LogLevel::ALERT|LogLevel::CRITICAL|LogLevel::ERROR|LogLevel::WARNING|LogLevel::NOTICE|LogLevel::INFO|LogLevel::DEBUG */
dcc855d
No branches or pull requests
Given the class example at https://psalm.dev/docs/annotating_code/typing_in_psalm/#specifying-stringint-options-aka-enums
it's common to have a list of enum values, that belong together. Usually a list of possible statuses, e.g.
Listing all possible statuses would be boring, as such i suggest
Additionally it could allow any const using
Subject::* $status
, but it looks less like a known const type :/ so it could be confusing to reason about.The text was updated successfully, but these errors were encountered: