Skip to content

Conversation

@dai-shi
Copy link
Member

@dai-shi dai-shi commented May 4, 2024

If we have main.tsx, we can place an error boundary there.
However with managed mode or nested routes, we may want to place an error boundary in RSC.
This enables to use previous elements on client with some condition. It only works with "static" layout.
This is experimental. We should add tests for this to keep the capability, if possible.

@vercel
Copy link

vercel bot commented May 4, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
waku ⬜️ Ignored (Inspect) Visit Preview May 7, 2024 10:59pm

@codesandbox-ci
Copy link

codesandbox-ci bot commented May 4, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@dai-shi dai-shi mentioned this pull request May 4, 2024
@dai-shi dai-shi marked this pull request as ready for review May 7, 2024 02:46
@dai-shi dai-shi merged commit ad7f29a into main May 7, 2024
@dai-shi dai-shi deleted the client/unstable-prev-fallback branch May 7, 2024 23:33
dai-shi pushed a commit that referenced this pull request Jul 10, 2024
It covers #696 and #741.
The test aims at how to implement auth features on the app side.

Considerations:
1. Our client router has to handle 4xx errors that the server responds
2. Middleware can be a validator to respond to 200 or 4xx status on
requests

I'm so glad to send my first PR to Waku, thank you!
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.

2 participants