Repository navigation
docs(platform): useChat backend wording for 0.6.0, and server-route examples - #356
Merged
Merged
Conversation
…xamples for sendMessage and submitToolCallInput #354 changed how a send or an answer ends, so the intros that said a failure sets `error` now say when it does. The Backend calls closing paragraph is split into the route-handler case and the server-action case, without colons. sendMessage() gets a route handler and a server action that waits a few seconds for a refusal, modeled on the starter's waitForRefusal. submitToolCallInput() gets a route handler that forwards extra_user_input, which Submit tool-call input now documents. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
🚀 Package Preview Available! (
|
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.57-pr.356.0052aedPrefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.57-pr.356.0052aed"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.57-pr.356.0052aed"
}
}
Preview published to npm registry — try new features instantly! |
adamfri
approved these changes
Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #354. Updates the
useChatreference for how a send or an answer ends in 0.6.0, and adds the server-route examples that were waiting on it.Wording
error. The second covers Next.js server actions, which should wait a few seconds for a refusal and then resolve.error". They now say it's set when Base44 refuses the request, or when the backend fails before Base44 has the prompt or answer. A question reopens only in that case.Examples
sendMessage()has two tabs. One is a route handler that forwards the request. The other is a server action that races the request against 3 seconds and logs a failure that arrives later, modeled onwaitForRefusalinbase44-platform-starter.submitToolCallInput()has a route handler that forwardstool_call_id,action, andextra_user_input.extra_user_inputis now a documented field on Submit tool-call input, andmessage_idstays private, so the example leaves it out.Each route checks in a comment that the signed-in user may use the app before forwarding anything.
All three examples type-check in strict mode.
npm testinpackages/platformpasses, and the docs build has no warnings.After this merges, the Platform SDK reference needs regenerating in mintlify-docs.
@base44/platform0.6.0 is already published.🤖 Generated with Claude Code