Skip to content

Latest commit

 

History

History
72 lines (46 loc) · 3.31 KB

CONFLICTS.md

File metadata and controls

72 lines (46 loc) · 3.31 KB
Raw

CONFLICTS

This document explains why certain conflicts were added to composer.json and references related issues.

  • symfony/cache": "^6.0, "symfony/amqp-messenger": "^6.0", "symfony/doctrine-messenger": "^6.0", "symfony/error-handler": "^6.0", "symfony/redis-messenger": "^6.0", "symfony/stopwatch": "^6.0", "symfony/twig-bridge": "^6.0", "symfony/var-dumper": "^6.0", "symfony/var-exporter": "^6.0",:

    Symfony in version 5.2 is installing amqp-messenger, doctrine-messenger, error-handler, redis-messenger, stopwatch, twig-bridge, var-dumper, var-exporter 6.0, which is not compatible with the current version of Sylius. This is not happening for Sf4.4, Sf5.3, Sf5.4.

  • symfony/password-hasher": "^6.0:

    Symfony in version 5.3 change password hashing logic, and in version 6.0 they removed BC layer

  • doctrine/doctrine-bundle:2.3.0:

    This version makes Gedmo Doctrine Extensions fail (tree and position behaviour mostly).

    References: doctrine/DoctrineBundle#1305

  • jms/serializer-bundle:3.9:

    This version automatically registered DocBlockDriver, which is always turned on, while docblocks used in our code are not usable with it. Sample error: Can't use incorrect type object for collection in Doctrine\ORM\PersistentCollection:owner

    References: schmittjoh/JMSSerializerBundle#844

  • symfony/serializer:4.4.19|5.2.2:

    These versions of Symfony Serializer introduces a bug with trying to access some private properties that don't have getters.

    References: symfony/symfony#40004

  • symfony/doctrine-bridge:4.4.16:

    This version of Doctrine Bridge introduces a bug that causes an issue related to ChannelPricing mapping.

    References: Sylius/Sylius#11970, symfony/symfony#38861

  • symfony/property-info:4.4.22|5.2.7:

    These versions of Symfony PropertyInfo Component introduce a bug with resolving wrong namespace for some translation entities in Swagger UI docs for API.

    The potential solution would be to explicitly define these translation entities as API resources with proper serialization.

    Probably introduced in: symfony/symfony#40811

In this section we keep track of the reasons, why some restrictions were added to the requires section of composer.json

  • doctrine/dbal:^2:

    In doctrine/dbal:^3 doctrine column type json_array has been removed creating error during a doctrine migration

    Error:  Migration Sylius\Bundle\CoreBundle\Migrations\Version20201130071338
failed during Execution.
In Exception.php line 125:
Unknown column type "json_array" requested. Any Doctrine type that you use   
has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get  
a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(  
). If this error occurs during database introspection then you might have f  
orgotten to register all database types for a Doctrine Type. Use AbstractPl  
atform#registerDoctrineTypeMapping() or have your custom types implement Ty  
pe#getMappedDatabaseTypes(). If the type name is empty you might have a pro  
blem with the cache or forgot some mapping information.

    References: Sylius/Sylius#13211