8000 [VarExporter] Fix exporting objects with readonly properties by nicolas-grekas · Pull Request #45891 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[VarExporter] Fix exporting objects with readonly properties #45891

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

Merged
merged 1 commit into from
Mar 30, 2022

Conversation

nicolas-grekas
Copy link
Member
Q A
Branch? 4.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #45886
License MIT
Doc PR -

@carsonbot carsonbot added this to the 4.4 milestone Mar 30, 2022
@nicolas-grekas nicolas-grekas changed the title [HttpClient] fix sending PUT requests with curl [VarExporter] Fix exporting objects with readonly properties Mar 30, 2022
@carsonbot carsonbot changed the title [VarExporter] Fix exporting objects with readonly properties [HttpClient] Fix exporting objects with readonly properties Mar 30, 2022
@fabpot
Copy link
Member
fabpot commented Mar 30, 2022

Thank you @nicolas-grekas.

@fabpot fabpot merged commit 5762970 into symfony:4.4 Mar 30, 2022
@nicolas-grekas nicolas-grekas deleted the ve-readonly branch March 30, 2022 17:41
@carsonbot carsonbot changed the title [HttpClient] Fix exporting objects with readonly properties [VarExporter] Fix exporting objects with readonly properties Mar 30, 2022
This was referenced Apr 2, 2022
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
0