Add interstitial page for admin event registration creation#1272
Merged
Add interstitial page for admin event registration creation#1272
Conversation
When an admin creates an event registration, instead of silently redirecting, show a confirmation page with optional follow-up actions: create a user account, send a system invite, send the registration confirmation email, and send the admin FYI email. Non-admin users retain the existing direct redirect behavior. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add confirm.html.erb to EXPECTED_MAPPINGS in page_bg_class alignment spec - Force lazy let evaluation before expect blocks that assert User.count changes, preventing factory side effects from inflating the count Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR and why is this important?
How did you approach the change?
EventRegistrationsController#createconfirm(GET) andprocess_confirm(POST) member routes onevent_registrationsEventRegistrationServices::ProcessConfirmationservice to handle the four optional actionsconfirm?andprocess_confirm?policy rulesUI Testing Checklist
Anything else to add?
admin-only bg-blue-100background, white card)UsersControllerfor user creation andPublicRegistrationfor notification sending🤖 Generated with Claude Code