Skip to content

[6.2] [Yaml] Dumper fix and refactor #46731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 15 commits into from

Conversation

donquixote
Copy link
Contributor

@donquixote donquixote commented Jun 21, 2022

Q A
Branch? 6.2 or 6.1 TBD
Bug fix? yes
New feature? no, unless you count increased tests and dumping more values
Deprecations? no
Tickets Fix #46725, #46718, #46728 partly
License MIT
Doc PR -

Check individual commits when reviewing!
The idea is that every commit should have a passing test.

@donquixote donquixote requested a review from xabbuh as a code owner June 21, 2022 19:47
@carsonbot carsonbot added this to the 6.2 milestone Jun 21, 2022
@donquixote donquixote force-pushed the yaml-Dumper-fix-and-refactor branch from 8c2c741 to 0b2f879 Compare June 21, 2022 20:16
@donquixote
Copy link
Contributor Author

Btw we could do evern more refactoring, but I want to preserve BC even for those who extend the Dumper class.

E.g. we could have the main ->dump() method be called only for the top level, and then use a different ->dumpRecursive() method. But this would break extending classes.

I also would like to have an option to save a line break for map inside sequence as requested in #15782. But better do this in a follow-up.

@donquixote
Copy link
Contributor Author

Fails seem unrelated.

@xabbuh
Copy link
Member

xabbuh commented Jun 22, 2022

Can you send the extension of the existing tests as a separate PR against the 4.4 branch please?

@donquixote
Copy link
Contributor Author

#46739

@nicolas-grekas
Copy link
Member

#46739 is now merged up to 6.2. Can you please rebase this PR?
Note that it'd be great to fix those @todo before merging, on 4.4 also.

Status: needs work.

@donquixote
Copy link
Contributor Author

@nicolas-grekas
Thanks!
What is a good base to rebase on?
We want to merge this into all branches later, right?

@donquixote
Copy link
Contributor Author

If I rebase on 4.4, do we want to support PHP 7.1?
The composer.json says so.
With 7.1 we cannot even use composer2 :)
But maybe this is exactly the point, to support legacy projects.

I am not sure if we actually do want to go for 4.4, so I make that a separate PR and we can choose.

@donquixote donquixote changed the title [Yaml] Dumper fix and refactor [6.2] [Yaml] Dumper fix and refactor Aug 3, 2022
@fabpot
Copy link
Member

fabpot commented Aug 3, 2022

Any reactorting must be done in 6.2.

@donquixote donquixote force-pushed the yaml-Dumper-fix-and-refactor branch from 0b2f879 to 7752a93 Compare August 3, 2022 11:16
@donquixote donquixote force-pushed the yaml-Dumper-fix-and-refactor branch from 7752a93 to 84cb847 Compare August 3, 2022 11:20
@nicolas-grekas nicolas-grekas modified the milestones: 6.2, 6.3 Nov 5, 2022
@xabbuh
Copy link
Member

xabbuh commented Nov 25, 2022

I fail to see the added benefit these changes bring, thus 👎 from my side on these changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Yaml] Dumper: TaggedValue at top level fails unless inline.
5 participants