-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[RNMobile] Add API fetch test helper #50391
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
/** | ||
* WordPress dependencies | ||
*/ | ||
import apiFetch from '@wordpress/api-fetch'; | ||
|
||
/** | ||
* Sets up the `apiFetch` library for testing by mocking request responses. | ||
* | ||
* Example: | ||
* | ||
* const responses = [ | ||
* { | ||
* request: { | ||
* path: `/wp/v2/media/1?context=edit`, | ||
* }, | ||
* response: { | ||
* source_url: 'https://image-1.jpg', | ||
* id: 1, | ||
* }, | ||
* }, | ||
* { | ||
* request: { | ||
* path: `/wp/v2/media/2?context=edit`, | ||
* }, | ||
* response: { | ||
* source_url: 'https://image-2.jpg', | ||
* id: 2, | ||
* }, | ||
* }, | ||
* ]; | ||
* setupApiFetch( responses ); | ||
* ... | ||
* expect( apiFetch ).toHaveBeenCalledWith( responses[1].request ); | ||
* | ||
* @param {object[]} responses Array with the potential responses to return upon requests. | ||
* | ||
*/ | ||
export function setupApiFetch( responses ) { | ||
apiFetch.mockImplementation( async ( options ) => { | ||
const matchedResponse = responses.find( | ||
( { request: { path, method } } ) => { | ||
return ( | ||
path === options.path && | ||
( ! options.method || method === options.method ) | ||
); | ||
} | ||
); | ||
return matchedResponse?.response; | ||
} ); | ||
} |
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.
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.
Would there be a benefit to logging an error here if there is no
matchedResponse
?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.
Actually, I originally added this condition but noticed the editor makes a set of requests always upon its initialization. This made me think that probably makes more sense to delegate checking what requests should be made or shouldn't to the test logic, instead here. In any case, we could add an option to make this function more restrictive and fail the test if an unexpected request is made. Maybe it's useful in some cases 🤔 .
For reference, the following requests are made when the editor is initialized:
/wp/v2/settings
/wp/v2/media
/wp/v2/pages
/wp/v2/block-patterns/patterns
/wp/v2/block-patterns/categories
/wp/v2/posts/post-id-<POST_GUID>
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.
Thank you for sharing the logic behind that decision, that makes sense to me.
I trust your judgement, but have a sense that the value would be relatively low. The current code looks good to me :) thanks again for expanding on the logic here.
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.
Ok, I'll merge the PR as-is, thanks!