Catch exception in reflection accessors about jint HOT 5 CLOSED

Can you create a sample test case about the problem and maybe expected error reporting? We also need to consider what can be exposed when usage is "sandboxed" as a SaaS service and .NET stack traces should be hidden by default.

from jint.

Also should note that default JS behavior is no-op:

Welcome to Node.js v18.17.0.
Type ".help" for more information.
> const person = {
...   set lang(value) {
...   }
... };
undefined
> person.lang
undefined

from jint.

As I know It's like an exception thrown by INotifyPropertyChanged.PropertyChanged. You'd better catch it like below,

var engine = new Engine(options =>
{
    options.AllowClr();
    options.CatchClrExceptions(e =>
    {
        e.PrintStackTrace();
        return true;
    });
});

from jint.

@SebastianStehle thoughts?

from jint.

Closing due to inactivity.

from jint.