Skip to content

[Messenger] [Redis] Remove BC layer around delete_after_ack option #42245

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
Jul 25, 2021

Conversation

chalasr
Copy link
Member

@chalasr chalasr commented Jul 23, 2021

Q A
Branch? 6.0
Bug fix? no
New feature? no
Deprecations? no
Tickets -
License MIT
Doc PR -

@chalasr chalasr requested a review from sroze as a code owner July 23, 2021 15:02
@carsonbot carsonbot added this to the 6.0 milestone Jul 23, 2021
@carsonbot carsonbot changed the title [Messenger][Redis] Remove BC layer around delete_after_ack option [Messenger] [Redis] Remove BC layer around delete_after_ack option Jul 23, 2021
trigger_deprecation('symfony/messenger', '5.3', 'The method "%s()" is deprecated, use getGlobalFailureReceiverName() instead.', __METHOD__);

return $this->globalFailureReceiverName;
}
Copy link
Member Author

@chalasr chalasr Jul 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unrelated change, but makes the bridge deprec-free. The class is internal so no need for a changelog entry (we didn't even add one when deprecating)

@chalasr
Copy link
Member Author

chalasr commented Jul 23, 2021

fabbot is wrong (still struggles with union types) - PR ready

Copy link
Member

@Nyholm Nyholm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you

@Nyholm
Copy link
Member

Nyholm commented Jul 25, 2021

Great work!

@Nyholm Nyholm merged commit 33a6d00 into symfony:6.0 Jul 25, 2021
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