first of all, we may not like that something like occweb is necessary. I understand that this is no full substitute for command line access. But oftentimes, this is simply not necessary.
Things like talk:monitor:calls or user:add simply don't need asynchronous capabilities. Whoever is using occweb should be bright enough to understand the limitations. We could add a warning sign at the beginning of each session. But that should be it.
Having said that, I suggest to check if a return value of a occ command is a string or object or array and do a var_dump() or print_r() or var_export() to show the actual contents instead of [object Object] or Array.
I would like to add a PR but only if this has any chance of merging in the near future.
first of all, we may not like that something like occweb is necessary. I understand that this is no full substitute for command line access. But oftentimes, this is simply not necessary.
Things like
talk:monitor:callsoruser:addsimply don't need asynchronous capabilities. Whoever is using occweb should be bright enough to understand the limitations. We could add a warning sign at the beginning of each session. But that should be it.Having said that, I suggest to check if a return value of a occ command is a string or object or array and do a var_dump() or print_r() or var_export() to show the actual contents instead of [object Object] or
Array.I would like to add a PR but only if this has any chance of merging in the near future.