We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
## 每次进去,获取今天新闻 // 前端 { command: 'todayNews', options: {}, } // 后端 jwt 判断用户,判断 command,查询,发送 { status: 200, data: { type: 'MultiText', content: [ { img: '', title: '', // 此种情况需要前端绑定时间,走 id Activity,请求参数 id: '' } ] } } ## 快递 ## 前端 { command: 'common', options: { data: 'xxxxx' } } ## 后端 能直接判断出,查询,发东西 发查快递,然后这样返回 { nextCommand: 'xxx', data: 'xxx' }
{ status: 200, data: { nextCommand: '', // 下次的命令, 没有就是空。用于对话交互, type: 'SingleText', content: 'xxxxx', } }
{ command: 'common' // 默认 common,直接指定,或者从 nextCommand 获取。先后顺序: 指定 -> nextCommand -> common。nextCommand 每次请求都刷新屌。 options: { } }
// request 首页获取东西 { command: 'todayNews', options: {} } // reponse 判断是 todayNews 直接返回 { nextCommnd: '', type: 'MultiText', content: [{}, {}] } // request 直接输入了快递号 { command: 'common', optopns: { data: '123456677' } } // reponse 匹配到是全数字,知道是快递,返回 { nextCommand: '', type: 'xx', content: '' } // request 点了查饭卡 { command: 'common', options: { data: '差饭卡' } } // response 判断 data 知道是查饭卡 { nextCommond: 'getFoodCard', type: 'xx', content "xx" // 给几个可选项? } // 一中情况 request 选择了1, { command: ''getFoodCard, options:{ data: 1 } } // 另外一种情况: 输了其他的,也没有什么耦合
这样不用单独记录每个的状态,由这种 command 的标记直接到相应状态,转移用 nextCommand
The text was updated successfully, but these errors were encountered:
为避免特殊情况发生,下面的 scrollview 加退出有无必要?
哪种情况会陷入状态循环?
Sorry, something went wrong.
No branches or pull requests
状态机放前端还是后端
前端:
后端:
思考
服务端数据格式
例子
这样不用单独记录每个的状态,由这种 command 的标记直接到相应状态,转移用 nextCommand
主动推送怎么实现?
合理性?
The text was updated successfully, but these errors were encountered: