🌟 fix: Handle Assistants Edge Cases, Improve Filter Styling (#2201)

* fix(assistants): default query to limit of 100 and `desc` order

* refactor(useMultiSearch): use object as params and fix styling for assistants

* feat: informative message for thread initialization failing due to long message
This commit is contained in:
Danny Avila 2024-03-25 08:55:33 -04:00 committed by GitHub
parent a4f4ec85f8
commit 8fc52348e8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 71 additions and 24 deletions

View file

@ -24,6 +24,8 @@ type SelectDropDownProps = {
optionsClass?: string;
subContainerClassName?: string;
className?: string;
searchClassName?: string;
searchPlaceholder?: string;
};
function SelectDropDown({
@ -43,6 +45,8 @@ function SelectDropDown({
subContainerClassName,
className,
renderOption,
searchClassName,
searchPlaceholder,
}: SelectDropDownProps) {
const localize = useLocalize();
const transitionProps = { className: 'top-full mt-3' };
@ -61,7 +65,12 @@ function SelectDropDown({
// Detemine if we should to convert this component into a searchable select. If we have enough elements, a search
// input will appear near the top of the menu, allowing correct filtering of different model menu items. This will
// reset once the component is unmounted (as per a normal search)
const [filteredValues, searchRender] = useMultiSearch<string[] | Option[]>(availableValues);
const [filteredValues, searchRender] = useMultiSearch<string[] | Option[]>({
availableOptions: availableValues,
placeholder: searchPlaceholder,
getTextKeyOverride: (option) => ((option as Option)?.label || '').toUpperCase(),
className: searchClassName,
});
const hasSearchRender = Boolean(searchRender);
const options = hasSearchRender ? filteredValues : availableValues;