-
In #45, it's brought up that `updateF7Select` does not allow for choices to be changed. After playing around with this, I've determined that there's a simple enough fix for this - changing the class o…
-
Hey Shelby, thanks for wrapping this all in a package!
I'm often working with multiple choice questions.
From previous experiments with a variety of LLMs I noticed that it's much "easier" for the…
-
When using llama-cpp-python the dict entry `choices` is always created.
I couldn't find any documentation on what `choices` stands for. While skimming the code it looks like there is always only one …
-
### The Feature
I want any generation that has N choices:
- To have all of the choices put under one span, for instance if the generation name was "X Chain of Thought", I want the span to be named…
-
[Extending this comment as I explore the code more]
Without the original authors, the backstory of the special remote isn't fully clear, but the - at many points very convoluted/clunky - implementa…
-
I really like using `form_choices` to guide my user into inputting into the create form.
However, it's limiting in the sense that my users can't use anything else not defined in form_choices.
…
-
Feature Request: Are we able to get the list of choices from the ChoiceParameterDefinition job parameter type?
-
**What you were expecting:**
When using custom choices, any changes to those choices should be reflected in the options.
**What happened instead:**
It seems that the initial options are being dis…
-
**suggestion (performance):** Consider simplifying font choices for better performance
The addition of numerous font families might impact performance. Consider if all these fonts are…
-
In simple_evaluate, what are the choices for verbosity? It's not mentioned in the function documentation. Currently, it is at "INFO" by default. Is there a verbosity level below this? INFO level print…