-
-
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
DBAL-867: Doctrine\DBAL\Driver\Connection should be marked as an internal interface #2105
Comments
Comment created by @guilhermeblanco: This issue was fixed some time ago. Commit reference: 5fdedc4 |
Comment created by @deeky666: [~guilhermeblanco] How is your commit reference related to this issue? |
Comment created by @guilhermeblanco: [deeky666] The suggestion about |
Comment created by stof: Your commit does not fix it at all. [~beberlei]'s comment was about the My issue is related to the description of the class itself: dbal/lib/Doctrine/DBAL/Connection.php Line 36 in aa2ed45
It still describes it as a wrapper around the driver connection, making other devs think that the right typehint in other libraries is the internal driver connection. See the discussion in the Symfony PR I linked |
Comment created by @guilhermeblanco: So... it's reopened. I'll look into this later today. |
Comment created by @Ocramius: [~guilhermeblanco] can you re-check this? |
Must have been addressed by #4159. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Jira issue originally created by user stof:
Currently, the main entry point
Doctrine\DBAL\Connection
is documented as a wrapper aroundDoctrine\DBAL\Driver\Connection
.This is very misleading and encourages other library to typehint against
Doctrine\DBAL\Driver\Connection
rather thanDoctrine\DBAL\Connection
. See symfony/symfony#10720 for the original discussion.However, the discussion in #414 (comment) implies that they should actually not be related together (but it cannot be fixed for BC reasons). The phpdoc should at least be changed
The text was updated successfully, but these errors were encountered: