Bendik Aagaard LynghaugandClaude Fable 5
c9c5caf3ff
Deploy / deploy (push) Successful in 1m3s
The 'previous question's resources until refresh' mystery: leptos's auto-generated server fn routes embed a hash that changes across builds. Every deploy therefore breaks every already-open tab - its wasm keeps calling /api/get_question<oldhash>, the new server answers 400 'Could not find a server function at the route', and client-side navigation quietly leaves the previous question's data on screen. Refresh loads the new wasm with matching hashes, which is why it always fixed it. Confirmed live: a pre-deploy client 400ed on get_question2970801986613442004 while the freshly served wasm calls get_question13103328088426240960, same source on both builds. Explicit endpoint names decouple the URL from the build. This deploy is the last breaking one; after it, old clients keep working. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
11 lines
213 B
Plaintext
11 lines
213 B
Plaintext
{
|
|
"permissions": {
|
|
"allow": [
|
|
"Bash(cargo check *)",
|
|
"Bash(git add *)",
|
|
"Bash(git commit -m 'Stable server fn endpoints: open tabs survive deploys *)",
|
|
"Bash(git push *)"
|
|
]
|
|
}
|
|
}
|