feat: predefined params

[urmauur]

Describe Your Changes

This pull request introduces several enhancements to the web-app project, focusing on UI improvements, new functionality for managing predefined parameters, and code organization. The most notable changes include the addition of a predefined parameters feature, updates to improve text truncation for assistant names, and the creation of a new configuration object for predefined parameters.

UI Improvements:

• Updated DropdownAssistant and Assistant components to use the line-clamp-1 class for truncating assistant names, ensuring consistent display across the application. (web-app/src/containers/DropdownAssistant.tsx - [1] web-app/src/routes/assistant.tsx - [2]

Predefined Parameters Feature:

• Added a predefined parameters section in the AddEditAssistant dialog, allowing users to select and add predefined parameters dynamically. (web-app/src/containers/dialogs/AddEditAssistant.tsx - web-app/src/containers/dialogs/AddEditAssistant.tsxR303-R359)
• Introduced a new paramsSettings object to define the available predefined parameters, including their keys, default values, titles, and descriptions. (web-app/src/lib/predefinedParams.ts - web-app/src/lib/predefinedParams.tsR1-R40)

Code Enhancements:

• Imported cn utility function for conditional class names and added IconMoodSmile to improve fallback UI for assistant avatars. (web-app/src/containers/dialogs/AddEditAssistant.tsx - [1] [2] [3]

Fixes Issues

• Closes #
• Closes #

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Add predefined parameters feature to AddEditAssistant dialog with UI and code enhancements.

• Predefined Parameters Feature:
  • Added predefined parameters section in AddEditAssistant dialog for dynamic selection and addition.
  • Introduced paramsSettings object in predefinedParams.ts to define available parameters with keys, default values, titles, and descriptions.
• UI Improvements:
  • Updated DropdownAssistant and Assistant components to use line-clamp-1 for truncating assistant names.
• Code Enhancements:
  • Imported cn utility for conditional class names and added IconMoodSmile for assistant avatar fallback in AddEditAssistant.tsx.

^{This description was created by for fd1c310. You can customize this summary. It will automatically update as commits are pushed.}

[louis-menlo]

Love it!

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to fd1c310 in 1 minute and 29 seconds. Click for details.

• Reviewed 179 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/containers/DropdownAssistant.tsx:97

• Draft comment:
  Refactored text truncation: replaced 'truncate' with 'line-clamp-1'. Verify cross-browser support.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. web-app/src/containers/dialogs/AddEditAssistant.tsx:238

• Draft comment:
  Enhanced avatar fallback by using IconMoodSmile for improved UI consistency.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. web-app/src/containers/dialogs/AddEditAssistant.tsx:323

• Draft comment:
  Predefined parameters logic reuses the last empty slot when adding new parameters. Ensure that handling of multiple empty slots or unexpected duplicates is as intended.
• Reason this comment was not posted:
  Confidence changes required: 30% <= threshold 50% None

4. web-app/src/routes/assistant.tsx:79

• Draft comment:
  Applied 'line-clamp-1' to assistant name for consistent text truncation in the UI.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. web-app/src/lib/predefinedParams.ts:12

• Draft comment:
  Typo: There is an extra trailing space at the end of the temperature description. Consider removing it for consistency.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While technically correct, this is an extremely minor formatting issue that doesn't affect functionality. It's the kind of thing that could be handled by an automated formatter or linter. The rules specifically say not to make comments that are obvious or unimportant. A trailing space in a description string is definitely unimportant. Maybe consistent string formatting is important for this project? Maybe there's a specific style guide that requires no trailing spaces? Even if there is a style guide, this is too minor to warrant a PR comment. It would be better handled by automated tools or general formatting guidelines. Delete this comment as it points out an extremely minor formatting issue that doesn't meaningfully impact the code.

Workflow ID: wflow_OHaXX6PKQcSEvD9U

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}