Exceptions from debug visual are silently caught and "eaten". about powerbi-visuals-tools

[spatney]

It does, you can either put a try-catch around it, or a method decorator like below to make this easy to re-use.

module powerbi.extensibility.visual {
    export function logExceptions() {
        return function (target: any, key: string, value: any) {
            return {
                value: function () {
                    let p = window.performance.now();
                    let result;
                    try {
                        result = value.value.apply(this, arguments);
                    } catch (e) {
                        console.error(e);
                        throw e;
                    }
                    return result;
                }
            }
        }
    }
}

and use it like below on the method you would like to log exceptions for.

@logExceptions()
public update(options: VisualUpdateOptions) {

We'll probably add a module for helpers like these soon enough.

[itslenny]

Thanks for pointing this out, @Knagis

There are a few techniques you can use for debugging your visual. I've added a page to the docs to explain them all: Debugging Guide

[Knagis]

This only handles the cases when the error is caused by code directly called from the visual. In this case the decorator approach would work.

However, if I use a library that uses setTimeout or requestAnimationFrame and fails there, the error would still be lost. Perhaps there is a way to get all errors logged by the host to be shown in the console. Even if that shows way too much information it would allow to quickly check if there are any errors when something seems not to be working. The break on caught exceptions is the minimum solution however it sometimes produces way too much noise. edit: seems to be not true