-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[TypeInfo] Remove deprecated code for non-array based collections #60988
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
base: 8.0
Are you sure you want to change the base?
Conversation
mttsch
commented
Jun 30, 2025
Q | A |
---|---|
Branch? | 8.0 |
Bug fix? | no |
New feature? | yes |
Deprecations? | no |
Issues | |
License | MIT |
I could not find a reference to the removed code in Symfony docs, thus I do not think they need updates. Also see the docs issue for the deprecations: symfony/symfony-docs#20602 |
042d3f7
to
d522388
Compare
```diff | ||
use Symfony\Component\TypeInfo\Type; | ||
|
||
-$type = Type::iterable(Type::string(), asList: true); | ||
+$type = Type::list(Type::string()); | ||
``` |
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 usually don't put diffs in changelogs 🙂
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 am sorry, but I am getting really mixed signals. In another PR, the UPGRADE contains before/after examples, the CHANGELOG did not. There it is suggested (by a Symfony Core Member) to also add before/after examples to the CHANGELOG. In this PR, it is suggested, to not do it.
I am happy to do the changes, but it appears that - unless I am misunderstanding things - there seems to be no consensus on this topic 🙂