-
-
Notifications
You must be signed in to change notification settings - Fork 932
chore(symfony): deprecations #6401
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
Conversation
* | ||
* @internal | ||
*/ | ||
final class PropertyInfoToTypeInfoHelper |
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.
I think this is good enough for now, but in the future we should migrate to use the new type class by default and convert it to the legacy type instead of the other way. This will likely improve performance, and will ease the maintenance.
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.
yes but while its experimental this is a good solution, also I don't really know why the Doctrine Extractor (MongoDB) is the only one impacted, there must be something in Symfony that doesn't cover the bc layer.
%ApiPlatform\\Api\\FilterInterface is deprecated in favor of ApiPlatform\\Metadata\\FilterInterface% | ||
|
||
%The "Symfony\\Bundle\\MakerBundle\\Maker\\MakeAuthenticator" class is deprecated, use any of the Security\\Make\* commands instead% | ||
%Since symfony/validator 7.1: Not passing a value for the "requireTld" option to the Url constraint is deprecated. Its default value will change to "true".% |
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.
nit: we could pass the value explicitly instead?
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.
not really:
- it's only in our tests
- we need to find a way to know if the option exists
- the default value is fine for us (as not really used by us)
therefore it won't break when updating
No description provided.