Skip to content

Conversation

@mspirkov
Copy link
Contributor

This topic has already been discussed here: #48

I believe that we need to slightly modify the logic for converting lists to strings.

For example, mixed[] is not the same as array. If we explicitly write mixed, it means that any value can be included. If we simply use array, it means that we have not explicitly specified what can be included in the array.

Static analyzers in particular distinguish between these cases. I suggest that we also distinguish between these cases here.

@mspirkov mspirkov marked this pull request as draft November 28, 2025 09:08
@mspirkov mspirkov marked this pull request as ready for review November 28, 2025 09:26
@jaapio jaapio merged commit fb05a34 into phpDocumentor:1.x Nov 28, 2025
32 checks passed
@jaapio
Copy link
Member

jaapio commented Nov 28, 2025

Thanks for this improvement!

fabpot added a commit to symfony/symfony that referenced this pull request Nov 29, 2025
…tting types from docblocks (xabbuh)

This PR was merged into the 6.4 branch.

Discussion
----------

[PropertyInfo] treat `mixed[]` the same as `array` when getting types from docblocks

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | account for phpDocumentor/TypeResolver#237
| License       | MIT

This fixes the PropertyInfo component tests by treating `mixed[]` as an alias of `array` sticking with the current behaviour even if that may technically not be fully correct to avoid unwanted behaviour changes for existing applications (see #62546 (comment)).

Commits
-------

2d94451 treat `mixed[]` the same as `array` when getting types from docblocks
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