Update Doc Service API middleware example - #2368
Merged
Merged
Conversation
Added a line to the example code to better clarify how to mutate results in middleware before returning them (or passing them to other middleware down the chain).
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
pwizla
approved these changes
Jan 23, 2025
pwizla
left a comment
pwizla
left a comment
Collaborator
There was a problem hiding this comment.
Thank you, @Gkleinereva!
The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a line to the example code to better clarify how to mutate results in middleware before returning them (or passing them to other middleware down the chain).
Per the instructions, this PR is ready to be merged.
What does it do?
This PR improves the Document Service API middleware example to better convey how to mutate query results prior to returning them to the client or other downstream middleware.
Why is it needed?
I had trouble implementing result mutations during an upgrade to Strapi 5. I thought this change could help future explorers figure it out a little bit faster.
Related issue(s)/PR(s)
N/A