Skip to content

test(e2e): Update react-router-6 test to avoid sending to Sentry #12313

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
May 31, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented May 31, 2024

Part of #11910

I renamed standard-frontend-react to react-router-6 as this is more descriptive (what does standard frontend even mean?).

This test now also uses the event proxy.

@mydea mydea requested review from lforst, Lms24 and andreiborza May 31, 2024 11:00
@mydea mydea self-assigned this May 31, 2024
@lforst
Copy link
Contributor

lforst commented May 31, 2024

what does standard frontend even mean?

In the beginning we had the idea of having standardized tests across frameworks. Obv this fell flat 😂

@mydea mydea force-pushed the fn/react-router-6 branch from 859a05f to d1978da Compare May 31, 2024 12:42
@mydea mydea merged commit 70f9c14 into develop May 31, 2024
108 checks passed
@mydea mydea deleted the fn/react-router-6 branch May 31, 2024 13:05
c298lee pushed a commit that referenced this pull request Jun 4, 2024
…12313)

Part of #11910

I renamed `standard-frontend-react` to `react-router-6` as this is more
descriptive (what does standard frontend even mean?).

This test now also uses the event proxy.
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.

3 participants