-
Notifications
You must be signed in to change notification settings - Fork 0
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
SLB-445: Integrate Waku with Decap #296
Conversation
aa541a4
to
8619a53
Compare
8619a53
to
6f54ee1
Compare
0fae94f
to
aa8245c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor things only.
In general, looks awesome 💪 The data flow is much easier to track now 🎉
@Leksat The green test on the admin ui is actually a false negative. The path can be accessed now, but the UI itself is broken because its not compatible with React 19. Either we manage to have two React versions in the repository without breaking Waku, or Decap compatibility is fixed at some point. Either way, I would defer this to another issue and close this PR to not have it generate conflicts for too long. |
A fetch error might include request and response objects that could contain circular references, potentially causing JSON.stringify to fail.
Description of changes
Motivation and context
Use Decap contents in Waku. Also create an architecture that allows Waku to fetch data from multiple sources through the same GraphQL Schema.
How has this been tested?