🐛 fix: Correct Endpoint/Icon Handling, Update Module Resolutions #5205
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danny-avila
force-pushed
the
fix/minor-issues
branch
from
ed05883 to
bf0f7a8
Compare
1 task
danny-avila
changed the title
dbirks
pushed a commit
to dbirks/LibreChat
that referenced
this pull request
Jan 7, 2025
…ny-avila#5205) * fix: agent modelSpec iconURLs not being recorded * fix: prioritize message properties over conversation defaults in icon data * fix: determine endpoint type from endpointsConfig * chore: type issue with setting.columnSpan * chore: remove redundant key indexing for keySchema * chore: bump version to 0.7.691 in package.json * chore: add stricter remark-gfm and mdast-util-gfm resolutions/overrides * chore: remove rollup override and bump vite-plugin-pwa * chore: reinstall remark-gfm for correct module resolution * chore: reinstall vite-plugun-pwa
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
endpointsConfiginHeaderOptions.tsxto ensure the correct endpoint type is used.MessageParts.tsx,MessageRender.tsx, andContentRender.tsxto accurately reflect message-specific icons.modelSpeciconURLsnot being recorded by addingiconURLtoendpointOptionand passing it through the agent services inclient.js,build.js, andinitialize.js.Change Type
Checklist