* refactor: scrollToEnd
* fix(validateConvoAccess): search conversation by ID for proper validation
* feat: Add unique index for conversationId and user in convoSchema
* refactor: Update font sizes 1 rem -> font-size-base in style.css
* fix: Assistants map type issues
* refactor: Remove obsolete scripts
* fix: Update DropdownNoState component to handle both string and OptionType values
* refactor: Remove config/loader.js file
* fix: remove crypto.randomBytes(); refactor: Create reusable function for generating token and hash
* fix: Update health endpoint URL
* refactor: use Constants for saved tag default value, do not place Saved as first always
* refactor: check trimmed currentText before appending parsedText in useSubmitMessage
* refactor: move `scrollToEnd()` to `createdHandler` and increase delay before execution slightly
* chore: Add back TypeScript linting rules for unnecessary conditions and strict boolean expressions
* chore: Update librechat-data-provider package.json version to 0.7.4.0
* feat: gpt-4o-2024-08-06 pricing for tx
* feat: add AWS models to tokenValues in tx.js for pricing transactions
* feat: Update tokenValues in tx.js for AWS models pricing
* refactor: add bedrock prefix values as well (temporary until we update value keys which includes context)
* refactor: optimize tag methods, remove rebuild
* refactor(tags): add lean db operations, fix updateTagsForConversation, remove rebuild button, only send convoId once
* refactor: Update BookmarkMenu to use Constants.NEW_CONVO constant for comparison
* style: Update BookmarkMenu styles and constants, use theming
* refactor: move tags query from package to client workspace
* refactor: optimize ConversationTag document creation and update logic
* style: Update BookmarkMenuItems to use theming
* refactor: JSDocs + try/catch for conversation tags API routes
* refactor: Update BookmarkNav theming classes and new data provider location
* fix: statefulness of conversation bookmarks
- move non-mutation hook to hooks/Conversation
- remove use of deprecated global convo
- update convo infinite data as well as current convo state upon successful tag add
* refactor: Update BookmarkMenu styles and constants, use theming
* refactor: Add lean option to ConversationTag deletion query
* fix(BookmarkTable): position order rendering esp. when new tag is created
* refactor: Update useBookmarkSucess to useBookmarkSuccess for consistency
* refactor: Update ConversationTag creation logic to increment count only if addToConversation is true
* style: theming
* 🌡️ feat: Periodic Health Check to prevent UI Inactivity Connection Errors
* feat: Add refetchOnWindowFocus option for health check
* feat: programmatically scroll to end when a chat request is initiated (and messages have rendered)
* 🛂 feat: Added Security for Conversation Access
* refactor: Update concurrentLimiter and convoAccess middleware to use isEnabled function for Redis check
* refactor: handle access check even if cache is not available (edge case)
* style: fix prompts icon shrinking in command popover
* fix: scroll into view behavior for mentions
* fix: always apply default font size if not found
* refactor: Update useMessageScrolling threshold and debounceRate
* refactor: Improve handling of key up events in useHandleKeyUp hook to only trigger for first char and fix linter issues
* refactor: Update Beta component styling with theme twcss variables
* refactor: theming for Settings, add toggle enable/disable keyboard commands
* fix: correctly handle openai assistants annotations
* fix: Handle adjacent identical citations only for our specific format
* fix: correctly handle adjacent identical citations
* refactor: make regex handling more robust
* fix: skip annotation condition, make regex handling more robust
* refactor: Handle FILE_PATH and FILE_CITATION annotation types in processMessages.spec.js
* ci: unit tests for real file path type annotations
* fix: get user-provided API key using environment variable names as keys
* feat: Add error handling for missing API key and search engine ID
* feat: Add GoogleSearch and TavilySearchResults specs for environment variables handling
---------
Co-authored-by: Dongwoo Jeong <dongwoo.jeong@lge.com>
* fix: regex issue extracting text with images in markdown
* fix: update addImages function to include only the first observed image path in the response message
* ci: tests for addImages function: correct image extraction
* fix(GoogleClient): linting
---------
Co-authored-by: Dongwoo Jeong <dongwoo.jeong@lge.com>
Co-authored-by: Dongwoo Jeong <dongwoo@duck.com>
* chore: playwright setup update
* refactor: update ChatRoute component with accessible loading spinner with live region
* chore(Message): typing
* ci: first pass, a11y testing
* refactor: update lang attribute in index.html to "en-US"
* ci: jsx-a11y dev eslint plugin
* ci: jsx plugin
* fix: Exclude 'vite.config.ts' from TypeScript compilation for testing
* fix(a11y): Remove tabIndex from non-interactive element in MessagesView component
* fix(a11y):
- Visible, non-interactive elements with click handlers must have at least one keyboard listener.eslintjsx-a11y/click-events-have-key-events
- Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element.eslintjsx-a11y/no-static-element-interactions
chore: remove unused bookmarks panel
- fix some "Unexpected nullable boolean value in conditional" warnings
* fix(NewChat): a11y, nested button issue, add aria-label, remove implicit role
* fix(a11y):
- partially address #3515 with `main` landmark
other:
- eslint@typescript-eslint/strict-boolean-expressions
* chore(MenuButton): Use button element instead of div for accessibility
* chore: Update TitleButton to use button element for accessibility
* chore: Update TitleButton to use button element for accessibility
* refactor(ChatMenuItem): Improve focus accessibility and code readability
* chore(MenuButton): Update aria-label to dynamically include primaryText
* fix(a11y): SearchBar
- If a form control does not have a properly associated text label, the function or purpose of that form control may not be presented to screen reader users. Visible form labels also provide visible descriptions and larger clickable targets for form controls which placeholders do not.
* chore: remove duplicate SearchBar twcss
* fix(a11y):
- The edit and copy buttons that are visually hidden are exposed to Assistive technology and are announced to screen reader users.
* fix(a11y): visible focus outline
* fix(a11y): The button to select the LLM Model has the aria-haspopup and aria- expanded attributes which makes its role ambuguous and unclear. It functions like a combobox but doesn't fully support that interaction and also fucntions like a dialog but doesn't completely support that interaction either.
* fix(a11y): fix visible focus outline
* fix(a11y): Scroll to bottom button missing accessible name #3474
* fix(a11y): The page lacks any heading structure. There should be at least one H1 and other headings to help users understand the orgainzation of the page and the contents.
Note: h1 won't be correct here so made it h2
* fix(a11y): LLM controls aria-labels
* fix(a11y): There is no visible focus outline to the 'send message' button
* fix(a11y): fix visible focus outline for Fork button
* refactor(MessageRender): add focus ring to message cards, consolidate complex conditions, add logger for setting latest message, add tabindex for card
* fix: focus border color and fix set latest message card condition
* fix(a11y): Adequate contrast for MessageAudio buttton
* feat: Add GitHub Actions workflow for accessibility linting
* chore: Update GitHub Actions workflow for accessibility linting to include client/src/** path
* fix(Nav): navmask and accessibility
* fix: Update Nav component to handle potential undefined type in SearchContext
* fix(a11y): add focus visibility to attach files button #3475
* fix(a11y): discernible text for NewChat button
* fix(a11y): accessible landmark names, all page content in landmarks, ensures landmarks are unique #3514#3515
* fix(Prompts): update isChatRoute prop to be required in List component
* fix(a11y): buttons must have discernible text
- Introduce getSafetySettings method for centralized safety settings
- Apply safety settings uniformly in sendCompletion for all models, including Gemini
- Ensure consistent safety settings application in getCompletion
- Update .env.example to clarify safety settings usage for both APIs
* feat: add tags property in Conversation model
* feat: add ConversationTag model
* feat: add the tags parameter to getConvosByPage
* feat: add API route to ConversationTag
* feat: add types of ConversationTag
* feat: add data access functions for conversation tags
* feat: add Bookmark table component
* feat: Add an action to bookmark
* feat: add Bookmark nav component
* fix: failed test
* refactor: made 'Saved' tag a constant
* feat: add new bookmark to current conversation
* chore: Add comment
* fix: delete tag from conversations when it's deleted
* fix: Update the query cache when the tag title is changed.
* chore: fix typo
* refactor: add description of rebuilding bookmarks
* chore: remove unused variables
* fix: position when adding a new bookmark
* refactor: add comment, rename a function
* refactor: add a unique constraint in ConversationTag
* chore: add localizations
* Allow LDAP login via username
This patch adds the option to login via username instead of using an
email address since the latter may not be unique or may change.
For example, our organization has two main domains and users have a log
and a short form of their mail address. This makes it hard for users to
identify what their primary email address is and causes a lot of
confusion. Using their username instead makes it much easier.
Using a username will also make it easier in the future to not need a
separate bind user to get user attributes. So, this is also a bit of
prep work for that.
* Update config.js
* feat: Enable LDAP login via username
This commit enables the option to login via username instead of using an email address for LDAP authentication. This change is necessary because email addresses may not be unique or may change, causing confusion for users. By using usernames, it becomes easier for users to identify their primary email address. Additionally, this change prepares for future improvements by eliminating the need for a separate bind user to retrieve user attributes.
Co-authored-by: Danny Avila <danny@librechat.ai>
* chore: jsdocs
* chore: import order
* ci: add ldap config tests
---------
Co-authored-by: Lars Kiesow <lkiesow@uos.de>
