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

Add :request to redirect.action_dispatch payload #45917

Conversation

jonathanhefner
Copy link
Member

Follow-up to #43755.

This adds the request object to the redirect.action_dispatch payload, for parity with redirect_to.action_controller.


It appears that, in general, we don't test instrumentation or payloads. I'm not sure whether that's intentional. We do document them though, so I thought it would be good to include a test in this PR.

Follow-up to rails#43755.

This adds the request object to the `redirect.action_dispatch` payload,
for parity with `redirect_to.action_controller`.
@skipkayhil
Copy link
Member

It appears that, in general, we don't test instrumentation or payloads. I'm not sure whether that's intentional.

👍 to testing too, notification payloads definitely seem like a public interface that should not be changing too often

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.

None yet

3 participants