Add unstable_runClientMiddleware API for dataStrategy #13395
Conversation
🦋 Changeset detectedLatest commit: 3be00d2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| return runMiddlewarePipeline( | ||
| args, | ||
| false, | ||
| () => singleFetchActionStrategy(args, basename), | ||
| handleMiddlewareError | ||
| ) as Promise<Record<string, DataStrategyResult>>; | ||
| return singleFetchActionStrategy(args, basename); |
There was a problem hiding this comment.
This goes back to effectively the original non-middleware implementation because we wrap middleware around the whole thing above
| basename, | ||
| getRouter | ||
| ); | ||
| return async (args) => args.unstable_runMiddleware(dataStrategy); |
There was a problem hiding this comment.
Use the new runMiddleware API to wrap middleware around our existing dataStrategy - instead of calling middleware independently for each fork in the dataStrategy
brophdawg11 force-pushed the brophdawg11/ds-run-middleware branch from 14229eb to cbb9d74 Compare brophdawg11 changed the title unstable_runMiddleware API for dataStrategyunstable_runClientMiddleware API for dataStrategy 
| 🤖 Hello there, We just published version Thanks! |
| 🤖 Hello there, We just published version Thanks! |
1 participant
Add the
unstable_runClientMiddlewareAPI todataStrategyto allow users to run middleware inside of customdataStrategyimplementations