feat(parse): allow custom HTTP client #61
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 introduces the ability to pass a custom HTTP client if you don't want to use Axios. This can be helpful if you're already using a client locally with features such as request deduping, caching, etc.
The second parameter can now be a function. When it is,
parse
recognizes you're trying to pass a custom client and not an Axios configuration object.Here's an example using
window.fetch
:I wanted to test the feature so I took the liberty to set up the testing environment. I'm using MSW to mock network calls, which is quite helpful as it allows to test without really making HTTP calls, but without having to mock the HTTP client itself.
I hope this feature makes it 🙂 Let me know if anything needs to change!
closes #60