Skip to content

[VarExporter] Remove per-property support, dropped in Symfony 7.0 #20660

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
Feb 18, 2025

Conversation

SherinBloemendaal
Copy link
Contributor

@carsonbot carsonbot changed the title Remove per-property support, dropped in Symfony 7.0 [VarExporter] Remove per-property support, dropped in Symfony 7.0 Feb 17, 2025
@xabbuh xabbuh added this to the 7.2 milestone Feb 17, 2025
@javiereguiluz javiereguiluz merged commit 344ec58 into symfony:7.2 Feb 18, 2025
3 checks passed
@javiereguiluz
Copy link
Member

Sherin, thanks and congrats on your first Symfony Docs contribution 🎉

In addition to merging your changes, we added a short notice to mention that this feature no longer exists (see 044c5aa). We usually do this when we remove something from code to help folks who are looking for that. Cheers!

javiereguiluz added a commit that referenced this pull request Feb 18, 2025
…d propertyScope in initiali… (SherinBloemendaal)

This PR was merged into the 6.4 branch.

Discussion
----------

[VarExporter] Add deprecation notice for propertyName and propertyScope in initiali…

Related to
* symfony/symfony#59790
* #20660

Commits
-------

63ee2e4 Add deprecation notice for propertyName and propertyScope in initializer (Symfony 6.4)
@javiereguiluz
Copy link
Member

Update: now I saw your nice #20661 pull request that does exactly that. So, I removed our notice in favor of yours. Thanks!

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.

4 participants