solidjs / solid / 39470342447

78%

main: 89%

push

github

feat(web): a server function reference can declare its own client send (#4170)

* feat(web): wrapServerFunctionsFetch, a send layer that composes with the app's fetch

An integration that answers some server-function requests itself (a
prerendered build's static artifacts) had to install itself as the
transport fetch, so it and an app's own configureServerFunctionsClient
({ fetch }) replaced each other depending on which ran last. A layer wraps
a send that reads the configured fetch at call time, so the order no
longer matters.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkjGmX4hAoiU9VhXNt7j3E

* perf(web): leave the transport's direct send in place until a layer is added

An unlayered app now ships no extra bytes: with wrapServerFunctionsFetch
tree-shaken, the send variable is never assigned and minifies away.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkjGmX4hAoiU9VhXNt7j3E

* refactor(web): a per-reference send instead of a global send layer

wrapServerFunctionsFetch added a second, global transport hook. A
reference can now declare its own send in its metadata instead
(withMeta(fn, { fetch: (address, init, next) => ... })): the transport uses
it for that function's requests with the app's configured send as next.
The intent lives on the declaration, the app's fetch stays the app's, and
there is nothing to order.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkjGmX4hAoiU9VhXNt7j3E

---------

Co-authored-by: Claude <noreply@anthropic.com>

756 of 1050 branches covered (72.0%)

Branch coverage included in aggregate %.

1103 of 1347 relevant lines covered (81.89%)

27.42 hits per line