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

feat(perf): Add page error context #28805

Merged
merged 1 commit into from
Sep 23, 2021
Merged

Conversation

k-fish
Copy link
Member

@k-fish k-fish commented Sep 23, 2021

Summary

Splitting off more pieces from the perf. landing v3. This is just a page error context which can be used without drilling setError everywhere. Added a simple test so it's not just implicitly tested.

Splitting off more pieces from the perf. landing v3. This is just a page error context which can be used without drilling setError everywhere. Added a simple test so it's not just implicitly tested.
@k-fish k-fish requested a review from a team as a code owner September 23, 2021 18:32
@k-fish k-fish enabled auto-merge (squash) September 23, 2021 18:57
};

export const PageErrorAlert = () => {
const {pageError} = useContext(pageErrorContext);
Copy link
Member

Choose a reason for hiding this comment

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

Can this use the usePageError hook you defined below?

@k-fish k-fish merged commit ad3d508 into master Sep 23, 2021
@k-fish k-fish deleted the feat/perf-add-page-error-context branch September 23, 2021 19:02
vuluongj20 pushed a commit that referenced this pull request Sep 30, 2021
Splitting off more pieces from the perf. landing v3. This is just a page error context which can be used without drilling setError everywhere. Added a simple test so it's not just implicitly tested.
@github-actions github-actions bot locked and limited conversation to collaborators Oct 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants