search

att / rcloud

Collaborative data analysis and visualization
http://rcloud.social
MIT License
430 stars 142 forks source link

trim console output for intended output #2685

Closed gordonwoodhull closed 4 years ago

gordonwoodhull commented 4 years ago

Every time there is a session log, it generates three logs in the browser console, making it hard to read stack traces or anything.

session.js:105 OOB send arrived: ['console.err']
session.js:12 forward_to_context, ctx=null, type=err, old.ctx=undefined
session_pane.js:70 session log:     91: self$.updateValue

session.js:105 OOB send arrived: ['console.err']
session.js:12 forward_to_context, ctx=null, type=err, old.ctx=undefined
session_pane.js:70 session log:     89: drawReactive

session.js:105 OOB send arrived: ['console.err']
session.js:12 forward_to_context, ctx=null, type=err, old.ctx=undefined
session_pane.js:70 session log:     76: origRenderFunc

We should only log OOB's if they are not handled, and that forward_to_context log is left over from initial development of output contexts and completely useless.