Skip to content

Be strict about deprecations #185

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 12, 2023
Merged

Be strict about deprecations #185

merged 1 commit into from
Mar 12, 2023

Conversation

jaapio
Copy link
Member

@jaapio jaapio commented Mar 12, 2023

The original implementation was causing issues with deprecations triggered in the wrong conditions. By introducing controlled deprecations using doctrine/deprecation we are able to handle this more properly.

The tests are updated to test the correct behavior, a new deprecation issue is created to track the deprecations.

fixes #178

The original implementation was causing issues with deprecations
triggered in the wrong conditions. By introducing controlled deprecations
using doctrine/deprecation we are able to handle this more properly.

The tests are updated to test the correct behavior, a new deprecation
issue is created to track the deprecations.
@jaapio jaapio force-pushed the controlled/deprecations branch from 3497c5f to b4d53cb Compare March 12, 2023 10:12
@jaapio jaapio merged commit 1534aea into 1.x Mar 12, 2023
@jaapio jaapio deleted the controlled/deprecations branch March 12, 2023 10:13
@williamdes
Copy link
Contributor

Thank you!
my company started sponsoring this organisation, I hope it helps

@jaapio
Copy link
Member Author

jaapio commented Mar 12, 2023

Thanks you for your sponsorship!

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.

Legacy nullable type detected, please update your code as you are using nullable types in a docblock
2 participants