-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Made the OCI8Statement class final #3820
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
|
||
## BC BREAK: Dropped handling of one-based numeric arrays of parameters in `Statement::execute()` | ||
|
||
The statement implementations no longer detect whether `$params` is a zero- or one-based array. A zero-based numeric array is expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably start adding @psalm-param list<T>
for these
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add Psalm to the build pipeline first? Consumers using Psalm will benefit from those annotations regardless but we want to make sure those annotations are valid and kept up to date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing - it's a big amount of work to get it to "like" our codebase though 😅
The
OCI8Statement::convertPositionalToNamedPlaceholders()
method is extracted to an internal utility class in order to enable making the class final. The corresponding test methods are extracted fromUtilTest
andOCI8StatementTest
to the dedicated test class.OCI8StatementTest
has been removed since it doesn't contain any more tests which is a good sign: we're not testing any driver-specific implementation details on the driver class itself.