Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
gadenbuie pushed 1 commit to main posit-dev/py-shiny
- feat(chat): Use `wrap: pre` so that "text" messages appear as-written (#1778) ba97d6d
gadenbuie created a comment on a pull request on posit-dev/py-shiny
Failures are transient in airmass example and un-related, merging.
cpsievert pushed 2 commits to markdown-stream-component posit-dev/py-shiny
cpsievert opened a draft pull request on posit-dev/py-shiny
Add `ui.MarkdownStream`
This PR extracts the streaming markdown capabilities of `ui.Chat()` into another component: `ui.MarkdownStream()`. See the new files for example usage: * `shiny/api-examples/MarkdownStream/app-e...
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- First pass at ui.MarkdownStream 3acbd4c
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- First pass at ui.MarkdownStream bdcaef9
gadenbuie pushed 2 commits to chat/text-message-wrapping posit-dev/py-shiny
gadenbuie pushed 1 commit to main posit-dev/py-shiny
- refactor(chat): Flatten rules in chat.scss (#1779) e60dad5
gadenbuie closed a pull request on posit-dev/py-shiny
refactor(chat): Flatten rules in chat.scss
Small refactor to flatten nested rules in `chat.scss`, since the custom element rules don't need to be nested. Flatter rules are easier to modify from userland and I contend they're easier to main...
gadenbuie created a comment on an issue on posit-dev/py-shiny
> Also, providing control over the user's content type from `.append_message()` doesn't feel quite right since user messages are automatically appended purely client-side elmer appends messages se...
cpsievert created a comment on an issue on posit-dev/py-shiny
Also, providing control over the user's content type from `.append_message()` doesn't feel quite right since user messages are automatically appended purely client-side (i.e., the only reason you s...
gadenbuie created a comment on a pull request on posit-dev/py-shiny
> I'd be curious to see how you're using `content_type="text"` since we don't really expose this at the moment, but seems OK to me. Manually, but in line with #1780 I think it should be possible...
cpsievert created a comment on an issue on posit-dev/py-shiny
> the message's content_type is ultimately determined from the role. There's a bit more to this. With `role: "user"` we do currently fix it to `"semi-markdown"`, but for `role: "assistant"` you ca...
cpsievert created a comment on a pull request on posit-dev/py-shiny
I'd be curious to see how you're using `content_type="text"` since we don't really expose this at the moment, but seems OK to me.
cpsievert created a comment on a pull request on posit-dev/py-shiny
The inspiration for nesting is two-fold: 1. Reduce the chance of clashing with other rules 2. Provide a signal that the nested elements should only exist inside certain parent elements That ...
gadenbuie pushed 1 commit to chat/content-type-html posit-dev/py-shiny
- chore: restore `semi-markdown` b90c211
gadenbuie pushed 1 commit to chat/content-type-html posit-dev/py-shiny
- chore: restore `semi-markdown` 95f5b1c
gadenbuie opened a draft pull request on posit-dev/py-shiny
feat(chat): Improve markdown handling
Initially, this PR started by allowing `content_type` on `<shiny-user-chat>` to customize the content type of the user message (previously hard-coded to `"semi-markdown"). I still think that's a ...
gadenbuie pushed 2 commits to chat/content-type-html posit-dev/py-shiny
gadenbuie pushed 1 commit to chat/content-type-html posit-dev/py-shiny
- feat(chat): Remove semi-markdown, sanitize markdown to display unknown tags 3260e68