Skip to content
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

UX: Display deprecations to end-user #5674

Merged
merged 1 commit into from May 3, 2021

Conversation

keradus
Copy link
Member

@keradus keradus commented May 3, 2021

simplified approach of #3699

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 91.531% when pulling de44afe on keradus:master_depr into c4998e5 on FriendsOfPHP:master.

@keradus keradus merged commit 45987c9 into PHP-CS-Fixer:master May 3, 2021
@keradus keradus deleted the master_depr branch May 3, 2021 22:38
keradus added a commit that referenced this pull request May 13, 2021
…ues (PetrHeinz)

This PR was squashed before being merged into the 2.19 branch.

Discussion
----------

Utils - save only unique deprecations to avoid memory issues

With the #5674 merged, we have run into exhaustion of allowed memory pretty quickly, see https://github.com/shopsys/shopsys/pull/2308/checks?check_run_id=2511509379

Even though it would be better for us to fix all the deprecations, and we definitely plan to do it in the future, it will be rather time consuming and we would like to use the newer version in the meantime.

I propose to save the deprecation message only if it's unique. Because `array_unique` is called on the result afterwards, I see no issues with this approach.

Commits
-------

b9a839e Utils - save only unique deprecations to avoid memory issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants