Skip to content

Expose more of the fetch API#882

Merged
dmjio merged 2 commits into
dmjio:masterfrom
georgefst:expose-more-fetch
Apr 17, 2025
Merged

Expose more of the fetch API#882
dmjio merged 2 commits into
dmjio:masterfrom
georgefst:expose-more-fetch

Conversation

@georgefst
Copy link
Copy Markdown
Contributor

As discussed just now on Matrix.

For the type class, there's an argument for only exposing it through some internal module rather than from the top-level Miso module where it would clutter the haddocks with a pretty niche part of the API. I'll leave that up to @dmjio. Personally I'd seriously consider factoring out the whole fetch API in to a separate library, not tied to Miso, but that suggestion was, not unreasonably, firmly rejected.

Useful for users who want to avoid the complexity of Servant
This gives advanced users the flexibility to implement more complex APIs, in the same way that `servant-client` exposes `HasClient`.
@dmjio dmjio merged commit 7f16295 into dmjio:master Apr 17, 2025
3 checks passed
@dmjio
Copy link
Copy Markdown
Owner

dmjio commented Apr 17, 2025

For the record, there are separate fetch libraries that can be used, but I believe miso needs to have a featureful fetch / xhr solution internally as well that is part of the Miso module. Also, reducing dep. count is a goal too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants