use the HTTP facade instead of manually creating a new request #76
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.
This allows consuming applications to use Http::fake() to mock the FileMaker Data API.
Prior to 2.2.1, I was able to do something like this in applications to mock the DAPI for my app tests:
Since 7b94af3 specifically, I now get an error:
Because the
new PendingRequest()
does not know about the already-faked responses it should return, it tries to run real requests.Solution: upgrade Laravel to ^11.3.0 to take advantage of the new
Http::createPendingRequest()
😆Alternate solution for older apps: use
Http::acceptJson()
to create the pending request while retaining knowledge of faked requests.