Skip to content

solid-v2: document the server-function data address - #288

Draft
ryansolid wants to merge 1 commit into
mainfrom
server-function-data-address
Draft

solid-v2: document the server-function data address#288
ryansolid wants to merge 1 commit into
mainfrom
server-function-data-address

Conversation

@ryansolid

Copy link
Copy Markdown
Member

Summary

  • A cacheable raw Response is shaped by a request header nothing keys on solid#3094 gives scripted server-function calls their own data address, <endpoint>/data/<id>, leaving the bare <endpoint>/<id> to plain HTTP (form actions, direct callers).
  • The audit found no code impact in the v2 templates: fullstack and fullstack-tanstack configure the mount only, their servers route by prefix/fallthrough, and the TanStack integration keys on query keys and flight sources, not URL shapes.
  • The two READMEs' network-tab walkthroughs said POST /_server; they now name POST /_server/data/<id>, which is what readers will actually see.

Draft until the @solidjs/web release carrying the split ships and the templates' deps resolve to it.

Test plan

  • After the next @solidjs/web release: run the fullstack template, rename a user, confirm the network tab shows one POST /_server/data/<id>

Made with Cursor

solidjs/solid#3094 gives scripted calls their own address under the
endpoint (/_server/data/<id>); the network-tab walkthroughs now name
the path readers will actually see. No code change: both templates
configure the mount only, and dispatch is prefix-based.

Co-authored-by: Cursor <cursoragent@cursor.com>
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