Skip to content

[VarExporter] Fix exporting classes with __unserialize() but not __serialize() #48724

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

Conversation

fancyweb
Copy link
Contributor

Q A
Branch? 5.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets #48706 indirectly
License MIT
Doc PR -

This is an edge case not supported yet, highlighted by our own symfony/expression-language GetAttrNode class.

@nicolas-grekas nicolas-grekas force-pushed the var-exporter/fix-export-__unserialize-without-__serialize branch from 16d0b26 to 6ccb85e Compare December 22, 2022 10:10
@nicolas-grekas
Copy link
Member

Thank you @fancyweb.

@nicolas-grekas nicolas-grekas merged commit 2aedd16 into symfony:5.4 Dec 22, 2022
@fancyweb fancyweb deleted the var-exporter/fix-export-__unserialize-without-__serialize branch December 22, 2022 11:31
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.

3 participants