Problem/Motivation
Somehow #3280951: Drupal 10 compatibility did not include the composer.json to make this actually installable. An option would also be to remove it and let drupal.org fill it in automatically, then it only needs to be changed in one place.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork csv_serialization-3294354
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
berdirComment #4
berdirLooks like 2.x and 3.x have no default configuration set up and the configuration for 1.x is outdated and for D8, which can no longer be tested.
Comment #5
jhedstromThis makes sense!
Comment #7
berdirMost if not all of these changes are unnecessary/unrelated, you should not mix in coding standards improvements with other changes. For example, it might make sense to apply those changes to other branches too and it's easier to cherry-pick them if done separately.
Comment #8
m.stentaDoes this need to go back to "Needs work"? @Berdir's simple commit should be all that's necessary to resolve this issue.
@Diego Restrepo - can you open a new issue with your other changes so that this can be merged faster?
Comment #10
heddnReverted the code standard changes. We're now back to simply the drupal core version range changes in composer.json.
Comment #11
heddnManually tested this module on a Drupal 10.0.1 site. No errors. +1 on merging and tagging a Drupal 10 release.
Comment #12
andrewbelcher commented3.x contains changes to signatures of methods extending symfony classes. It isn't compatible with the version of symfony supported by D9, so 3.x needs to be D10 only.
Comment #13
berdirDid you try that? we discussed that in the linked issue and many but not all of these changes are forward compatible, meaning classes can be more strict than interfaces.
Comment #16
volegerIt makes sense to delete the line and get rid of the need to synchronize the info.yml file with the composer.json file for now. Added MR with line removal.
When #3005229: Provide optional support for using composer.json for dependency metadata will be in, we can move the core version requirement into composer.json.
Comment #17
pwolanin commentedIsn't it better to remove this requirement from composer.json?
Comment #18
voleger+ 1 for removal. See MR !13
Comment #19
volegerBoth MRs needs review and the final decision on what needs to be made with the problematic line of the composer.json file.
Comment #20
markdorisonMerging MR !13. Thank you to everyone in this issue for testing and providing great feedback!
Comment #22
markdorison