Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ai): add message renderer #5873

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Conversation

dbanksdesign
Copy link
Contributor

Description of changes

Adds the ability to define message renderer functions for text and images so that customers can render markdown without us taking a dependency on a markdown renderer.

Issue #, if available

Description of how you validated changes

Checklist

  • Have read the Pull Request Guidelines
  • PR description included
  • yarn test passes and tests are updated/added
  • PR title and commit messages follow conventional commit syntax
  • If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dbanksdesign dbanksdesign requested a review from a team as a code owner October 8, 2024 06:02
Copy link

changeset-bot bot commented Oct 8, 2024

🦋 Changeset detected

Latest commit: 2dd9988

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@aws-amplify/ui-react-ai Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

reesscot
reesscot previously approved these changes Oct 17, 2024
@@ -54,6 +55,11 @@ export interface AIConversation {

export type MessageVariant = 'bubble' | 'default';

export interface MessageRenderer {
text?: (message: string) => React.JSX.Element;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to expand the function definition here to allow an object so additional key/values can be included in the future?

  // example
  text?: (text: { content: string )) => React.JSX.Element;

calebpollman
calebpollman previously approved these changes Oct 17, 2024
Copy link
Member

@calebpollman calebpollman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

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.

4 participants