Jargon Clarification and Visual Response preferences are currently hardcoded into the Preferences panel. Might be better to update the conversation type in the back end to include the schema for applicable preferences and read them dynamically, so we aren't hardcoding new elements whenever preferences are added.
Right now this is somewhat specified by features that have userControlled set to true and do not have a slash command. Need to explore adding a type (boolean, number, etc) the way properties have and possibly being a bit more explicit about the fact these are preferences rather than features...
Jargon Clarification and Visual Response preferences are currently hardcoded into the Preferences panel. Might be better to update the conversation type in the back end to include the schema for applicable preferences and read them dynamically, so we aren't hardcoding new elements whenever preferences are added.
Right now this is somewhat specified by features that have
userControlledset to true and do not have a slash command. Need to explore adding a type (boolean, number, etc) the way properties have and possibly being a bit more explicit about the fact these are preferences rather than features...