CsvEncoder::encode must be compatible with Symfony\Component\Serializer\Encoder\EncoderInterface::encode

In symfony 6.2 the signature is:
public function encode(mixed $data, string $format, array $context = []): string
while in csv_serialization the signature:
public function encode($data, string $format, array $context = []):string

shouldn't we fix this?

This not being in the 3.x release causes WSOD on Drupal 9 installations.
Fatal error: Declaration of Drupal\csv_serialization\Encoder\CsvEncoder::encode($data, string $format, array $context = []): string must be compatible with Symfony\Component\Serializer\Encoder\EncoderInterface::encode($data, $format, array $context = []) in /var/www/html/web/modules/contrib/csv_serialization/src/Encoder/CsvEncoder.php on line 125

ddev composer require 'drupal/csv_serialization:^3.0' -W

installed beta.

$ ddev composer require 'drupal/csv_serialization:^3.0' -W
./composer.json has been updated
Running composer update drupal/csv_serialization --with-all-dependencies
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 2 updates, 0 removals
  - Upgrading doctrine/deprecations (v1.1.0 => v1.1.1)
  - Upgrading drupal/csv_serialization (2.1.0 => 3.0.0-beta1)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 2 updates, 0 removals
  - Downloading doctrine/deprecations (v1.1.1)
  - Downloading drupal/csv_serialization (3.0.0-beta1)
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
  - Upgrading doctrine/deprecations (v1.1.0 => v1.1.1): Extracting archive
  - Upgrading drupal/csv_serialization (2.1.0 => 3.0.0-beta1): Extracting archive
Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead.
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Package symfony/debug is abandoned, you should avoid using it. Use symfony/error-handler instead.
Package webmozart/path-util is abandoned, you should avoid using it. Use symfony/filesystem instead.
Generating autoload files
100 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found

I'll check, that makes sense. Thanks. 👍

I was getting issues upgrading this module to 3.0 when using a D9 install (currently moving to D10 but needed to upgrade this first). I was seeing the same error when running a drush updatedb:

Unable to decode output into JSON: Syntax error
Fatal error: Declaration of Drupal\csv_serialization\Encoder\CsvEncoder::encode($data, string $format, array $context = []): string must be compatible with Symfony\Component\Serializer\Encoder\EncoderInterface::encode($data, $format, array $context = []) in /var/www/html/web/modules/composer/csv_serialization/src/Encoder/CsvEncoder.php on line 125   

Using the composer require drupal/csv_serialization:^2.0 || ^3.0 command allowed me to get past this and I'm assuming that this will work for D10 also once I start that upgrade process.

Thanks for the tip @bcdev, that worked for me :)

Hello
Thanks @bcdev, applied your tips and seem to be ok now.

Just a followup for #15 – you will want to include ^2.0 || ^3.0 directly in your composer file. Running the listed command will just require 2.0, since composer sees the pipes as a new command. The module will still show in Upgrade Status as needing to be updated, but at least it should be prepped to upgrade after the move to D10.

Echoing @bwoods in #18 the instructions given in https://www.drupal.org/project/upgrade_status read:
composer require drupal/csv_serialization:^2.0 || ^3.0
whereas actually we need the quotes like:
composer require 'drupal/csv_serialization:^2.0 || ^3.0'
or composer.json will not be updated as you'd expect.
Further, if you're already on 2.1, you shouldn't specify just 2.0 but ^2.1 || ^3.0 I think. Maybe the best move is less specific, since we don't yet _know_ what the 3.x version will be at the time of finally pulling the trigger: ^2.1 || ^3. Is this message dictated by this module or something else?

I propose this patch to fix error when drush cr

#19 works perfectly. Thanks @texas-bronius.

this doesnt work for D10 because the 3xdev doesnt work for d10 and the 4.0 version has the same issue still

patch for ^4.0, I didn't test it