-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Deprecate omitting the alias in QueryBuilder::update() and delete() #9765
Conversation
Co-authored-by: Alexander M. Turek <me@derrabus.de>
Co-authored-by: Alexander M. Turek <me@derrabus.de>
The issue is just fine. Can you please add a small test for each method that checks if the exception is being raised? |
Also, please run |
i'm only edited in github, i will try it later any special php version under which i should do that?
currently there isn't any exception but trigger warning, but i will check on how such test would be done |
Co-authored-by: Alexander M. Turek <me@derrabus.de>
Co-authored-by: Alexander M. Turek <me@derrabus.de>
Co-authored-by: Alexander M. Turek <me@derrabus.de>
i will update the method description from update and delete later too so it is more clear that the two wanted use cased are:
|
There is a |
The failing tests look related. Did you execute the tests locally? |
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.
Looks good to me. Thank you for your PR.
The PR is still flagged as draft. Is there anything left to do from your side?
Co-authored-by: Alexander M. Turek <me@derrabus.de>
i was thinking about adding the info into the method description telling the user that they should only do either zero or two arguments. But i might not be good with the wording :p does the method description needs extra info that it might raise a deprecation or later an exception in the future? |
Feel free to do so, but I don't think it's necessary. Write the documentation that would've helped you. Don't worry too much about the wording.
No. I don't think we need to document the deprecation explicitly here. If you add extra documentation, just say that either none or both parameters have to be passed. |
… methods update() and delete() Co-authored-by: Alexander M. Turek <me@derrabus.de>
* 2.13.x: Deprecate omitting the alias in QueryBuilder (doctrine#9765) Run tests on PHP 8.2 (doctrine#9840) PHPStan 1.7.13 (doctrine#9844) Flip conditional extension of legacy AnnotationDriver class (doctrine#9843) PHP CodeSniffer 3.7 (doctrine#9842) Make Reflection available to ConvertMappingCommand (doctrine#9619) Add missing property declaration Use proper API for introspection of tables
Closes #9733
Should the Trigger warning has the link to the Issue or to the PR?