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

[Feature Request] Allow using TextGenerationWidget in place of ConversationalWidget when needed #521

Open
felladrin opened this issue Feb 29, 2024 · 2 comments
Labels

Comments

@felladrin
Copy link

felladrin commented Feb 29, 2024

Hi all,

Thank you for the ConversationalWidget addition. It's working great for my chat models. But I'd like to ask if you could add a way to set a repository to use TextGenerationWidget in place of ConversationalWidget when needed.

By the code, it doesn't seem to be possible, considering the "conversational" tag is added automatically.

$: widgetComponent =
model.pipeline_tag === "text-generation" && model.tags?.includes("conversational")
? (ConversationalWidget as typeof SvelteComponent)
: model.pipeline_tag && model.pipeline_tag in WIDGET_COMPONENTS
? WIDGET_COMPONENTS[model.pipeline_tag as keyof typeof WIDGET_COMPONENTS]
: undefined;

My use case is this base model, which has the "chat_template" because it is intended to be a foundation for chat models using ChatML, but at the same time, half of its pretraining was focused on text-completion; so it's not that good at chat, and for this reason, I'd prefer it displaying the TextGenerationWidget.


Another option would be removing the "conversational" tag from it, is there any way to do it by editing the Readme?

The current Readme is overriding the "tags",
image

but even so, the "conversational" tag is there.
image

@coyotte508
Copy link
Member

cc @julien-c @osanseviero

@julien-c
Copy link
Member

we could add a widget_type optional override in the metadata if we wanted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants