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
So, it's plausible that we could merge some parts of adhearsion-asr into Adhearsion core prior to Adhearsion 3.0: the settings, the PromptBuilder and the Result structure. We could not include the #ask and #menu controller methods, since they are the parts which are not backward compatible. There would not be a benefit to including either the AskGrammarBuilder (used to build grammars from :limit options to #ask) or the MenuBuilder (implementing the menu DSL, including grammar construction from #matches, retries, error/failure handling and invocation of #matches).
Merging these pieces into Adhearsion core would reduce the future effort required to merge adhearsion-asr into core, allow adhearsion-ivr to function without depending on adhearsion-asr, and thus allowing adhearsion-ivr to be merged in to core in the Adhearsion 2.x series, if this were desirable.
Additionally, in its current form, this gem provides similar functions to #ask. What it does not provide from adhearsion-asr is simple support for built-in grammars for common cases (from #ask, eg yes/no, DTMF grammars with digit limits or unlimited input up to a terminator) or automatic grammar construction from a list of possible options (from #menu, similar to VoiceXML Menus).
These features do not help the case for a merge into Adhearsion core, but would permit absorbing adhearsion-asr such that #ask and #menu might be deprecated entirely from Adhearsion core and maintained solely in adhearsion-asr, should we decide that this whole-controller implementation was preferable going forward.
Adhearsion-asr cannot be merged into Adhearsion core until Adhearsion 3.0 since it changes the API of core #ask and #menu methods on
CallController
.Particularly #menu is a candidate for closer integration with this gem.
The text was updated successfully, but these errors were encountered: