You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the configuration for the MODEL_TYPE setting uses SettingType.SELECT with predefined model values, such as "meta-llama/Llama-3.2-11B-Vision-Instruct". This approach limits flexibility because different providers might use different model names for the same model. Instead, we can use a direct string input for the model name.
if this valid, i want to work on this issue.
The text was updated successfully, but these errors were encountered:
No sir, I just want to implement type string instead of select because i find "meta-llama/Llama-3.2-11B-Vision-Instruct", for this same model different provider are using different model name.
Great intention 🙏 But I don't think we should do anything in this area AT THIS POINT IN TIME.
Because it is not too difficult to every contributor working with it to change the code if needed.
Adding this code now can also confuse new contributors since it introduces a baggage that has nothing to do with the purpose/objective of this project.
I am not going to close this, but just leave it here for contributors to implement after we have a fixed working core / direction. Thanks again.
Currently, the configuration for the MODEL_TYPE setting uses SettingType.SELECT with predefined model values, such as "meta-llama/Llama-3.2-11B-Vision-Instruct". This approach limits flexibility because different providers might use different model names for the same model. Instead, we can use a direct string input for the model name.
if this valid, i want to work on this issue.
The text was updated successfully, but these errors were encountered: