8000 [API] Conflict with symfony/property-info due to problem with wrong n… · Sylius/Sylius@dc01355 · GitHub
[go: up one dir, main page]

Skip to content

Commit dc01355

Browse files
committed
[API] Conflict with symfony/property-info due to problem with wrong namespaces of some translation entities
1 parent 960d349 commit dc01355

File tree

2 files changed

+10
-0
lines changed

2 files changed

+10
-0
lines changed

CONFLICTS.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,3 +53,12 @@ references related issues.
5353
`ParseError - vendor/symfony/polyfill-mbstring/bootstrap80.php:125:86 - Syntax error, unexpected '=' on line 125 (see https://psalm.dev/173) function mb_scrub(string $string, string $encoding = null): string { $encoding ??= mb_internal_encoding(); return mb_convert_encoding($string, $encoding, $encoding); }`
5454

5555
References: https://github.com/vimeo/psalm/issues/4961
56+
57+
- `symfony/property-info:4.4.22|5.2.7`:
58+
59+
These versions of Symfony PropertyInfo Component introduce a bug with resolving wrong namespace for some translation entities
60+
in Swagger UI docs for API.
61+
62+
The potential solution would be to explicitly define these translation entities as API resources with proper serialization.
63+
64+
Probably introduced in: https://github.com/symfony/symfony/pull/40811

composer.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,6 +166,7 @@
166166
"laminas/laminas-code": "^4.0.0",
167167
"symfony/doctrine-bridge": "4.4.16",
168168
"symfony/polyfill-mbstring": "^1.22.0",
169+
"symfony/property-info": "4.4.22 || 5.2.7",
169170
"symfony/serializer": "4.4.19 || 5.2.2"
170171
},
171172
"require-dev": {

0 commit comments

Comments
 (0)
0