feat: capture specific feedback form data to Sentry before recaptcha#45
Draft
thostetler wants to merge 1 commit intomasterfrom
Draft
feat: capture specific feedback form data to Sentry before recaptcha#45thostetler wants to merge 1 commit intomasterfrom
thostetler wants to merge 1 commit intomasterfrom
Conversation
When recaptcha is blocked, specific feedback forms lose user data. The general feedback form already mirrors submissions to Sentry — this replicates that pattern for associated references, missing/incorrect records, and correct abstract forms. Adds a shared sendFeedbackToSentry utility that resolves Sentry via whenSentryReady/window.Sentry and calls captureFeedback (with sendFeedback fallback). Each FormPreview now fires this as the first action in handleSubmit, before recaptcha, so data is never lost.
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
1 participant
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.
When recaptcha is blocked (ad blockers, network restrictions, timeouts),
the specific feedback forms (associated articles, missing references,
correct abstract) show an error and the user's work is lost. The general
feedback form already mirrors every submission to Sentry via
captureFeedback — this replicates that pattern for the three specific
forms so no submission data is ever lost.
that resolves Sentry via whenSentryReady/window.Sentry and calls
captureFeedback with sendFeedback fallback (same dual-path as navbar)
SubmitCorrectAbstract) now calls sendFeedbackToSentry as the first
action in handleSubmit, before recaptcha attempt
recaptcha failures specifically, the new utility captures user data)