Sign in
Join now
scn-chat
sharedcomputer.network
/
Star
Starred
Star
Something went wrong. Try again.
Fork
0
Eye filled
Watch
Watching
Watch
ATProto-based AI Assistant Chat interface.
Star
Starred
Star
Something went wrong. Try again.
Fork
Eye filled
Watch
Watching
Watch
Overview
Overview
Issues
Issues
1
1
Pulls
Pulls
Pipelines
Pipelines
scn-chat
/
apps
/
web
/
tests
/
features
/
conversation
/
components
6 files
at
admin-config-export
pouriade.com
·
A streaming reply's words fade in as they arrive, over the theme's enter duration, with Streamdown's 40ms between words, so a burst of them lands as a short cascade. markdown.css animates Streamdown's word spans with --animate-fade-in, since the app doesn't load Streamdown's stylesheet, and fades a list item's marker in by its color, which is all ::marker takes. Nothing animates under reduced motion. Code blocks and math appear as before, and a finished part renders without the spans. Two tests that found streamed text by its exact node now look past the word spans.
·
4w ago
59e19733
Composer.test.tsx
useChat, in features/conversation/chat.ts, is the open conversation as a chat, in the shape of the AI SDK's useChat without a message list of its own: the branch on screen and the messages behind it from the browser store, whether they are on their way or known empty, the reply running at the end of the branch, and send, regenerate, and stop, on top of useConversation, the reply follower, and useBranch. Every turn, from a send, an edit, or a regeneration, follows its reply, puts its new message on the branch, replacing m, and calls the view's onTurnStarted, with which ConversationView scrolls to the bottom, so regenerating now scrolls there too, as sending and editing did. useStartChat sends a new chat's first message, creating the chat and reusing it after a failed send. The composer only builds the message and hands it to send, so it no longer knows the chat's key, creates chats, or posts, and BranchComposer and NewConversation pass send through. useBranch absorbs useScrollToFocus, scrolling to a message the URL focuses while a picked one keeps the scroll, so the shared page now scrolls to a linked message too. useConversationActions keeps renaming, the instructions, and syncing, and the conversation's one alert shows whichever action or turn ran last. Its tests cover sending, regenerating, stopping, the running reply, starting a chat, and scrolling to a focus, and the composer's tests check the message it hands to send. The web UI spec describes the chat.
1mo ago
ComposerFrame.test.tsx
useChat, in features/conversation/chat.ts, is the open conversation as a chat, in the shape of the AI SDK's useChat without a message list of its own: the branch on screen and the messages behind it from the browser store, whether they are on their way or known empty, the reply running at the end of the branch, and send, regenerate, and stop, on top of useConversation, the reply follower, and useBranch. Every turn, from a send, an edit, or a regeneration, follows its reply, puts its new message on the branch, replacing m, and calls the view's onTurnStarted, with which ConversationView scrolls to the bottom, so regenerating now scrolls there too, as sending and editing did. useStartChat sends a new chat's first message, creating the chat and reusing it after a failed send. The composer only builds the message and hands it to send, so it no longer knows the chat's key, creates chats, or posts, and BranchComposer and NewConversation pass send through. useBranch absorbs useScrollToFocus, scrolling to a message the URL focuses while a picked one keeps the scroll, so the shared page now scrolls to a linked message too. useConversationActions keeps renaming, the instructions, and syncing, and the conversation's one alert shows whichever action or turn ran last. Its tests cover sending, regenerating, stopping, the running reply, starting a chat, and scrolling to a focus, and the composer's tests check the message it hands to send. The web UI spec describes the chat.
1mo ago
ConversationView.test.tsx
A streaming reply's words fade in as they arrive, over the theme's enter duration, with Streamdown's 40ms between words, so a burst of them lands as a short cascade. markdown.css animates Streamdown's word spans with --animate-fade-in, since the app doesn't load Streamdown's stylesheet, and fades a list item's marker in by its color, which is all ::marker takes. Nothing animates under reduced motion. Code blocks and math appear as before, and a finished part renders without the spans. Two tests that found streamed text by its exact node now look past the word spans.
4w ago
MessageView.test.tsx
A streaming reply's words fade in as they arrive, over the theme's enter duration, with Streamdown's 40ms between words, so a burst of them lands as a short cascade. markdown.css animates Streamdown's word spans with --animate-fade-in, since the app doesn't load Streamdown's stylesheet, and fades a list item's marker in by its color, which is all ::marker takes. Nothing animates under reduced motion. Code blocks and math appear as before, and a finished part renders without the spans. Two tests that found streamed text by its exact node now look past the word spans.
4w ago
PendingReply.test.tsx
A pending reply is drawn by one module, PendingReply.tsx: its waiting or live header, its stream, and the lines about a wait, a busy provider, or a lost stream, until its finished record replaces it. MessageView uses it while a record is pending, and it follows the conversation the FollowedConversation context names, which ConversationView provides, so MessageView and BranchView no longer take pending and live slots and BranchRow no longer checks the status. The stream's part views get the pending record rather than a made-up one, and the model's name comes from MessageView alone. LiveAuthor.tsx, ReplyStream.tsx, and StreamingReply.tsx are gone. A conversation test streams a reply, then has its record arrive, and checks the time it thought carries over and its text shows once.
4w ago
RecordDetails.test.tsx
The web app's message records are typed as the lexicon's MessageRecord, and a conversation's info as InfoRecord, from the local copy, which holds only records the server validated, through BranchMessage to the message, status, details, part, and tool views, so their reads need no casts. src/shared/message.ts holds what a status means, isPending and isFinished, which counts a status another client wrote that this app doesn't know as neither, along with a message's parts, whether it is encrypted, and who wrote it, in place of the checks written out in the message view, the message actions, the chat, the reply follower, and tool status. Tests build records with messageRecord in tests/helpers/records.ts, and the status rules are tested once.
4w ago