Skip to content
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

chore(symfony): deprecations #6401

Merged
merged 7 commits into from
Jun 1, 2024
Merged

chore(symfony): deprecations #6401

merged 7 commits into from
Jun 1, 2024

Conversation

soyuka
Copy link
Member

@soyuka soyuka commented May 31, 2024

No description provided.

phpstan.neon.dist Outdated Show resolved Hide resolved
*
* @internal
*/
final class PropertyInfoToTypeInfoHelper
Copy link
Member

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.

Copy link
Member Author

@soyuka soyuka Jun 1, 2024

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.

@@ -25,3 +25,4 @@
%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".%
Copy link
Member

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not really:

  1. it's only in our tests
  2. we need to find a way to know if the option exists
  3. the default value is fine for us (as not really used by us)

therefore it won't break when updating

@soyuka soyuka merged commit a655ddf into api-platform:3.3 Jun 1, 2024
76 checks passed
soyuka added a commit to soyuka/core that referenced this pull request Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants