Readonly engine about jint HOT 5 CLOSED

I had a look to the code and it seems that this is actually the relevant method:

But it is internal and all relevant types are internal as well.

This could be implemented by making a ReadonlyReflectionAccessor that wraps the actual accessor or something like that. Perhaps with a similar delegate like the member filter.

I can probably provide a PR for that.

from jint.

I was not aware that there is AllowClrWrite.

from jint.

So if this is only about interop scenarios, is the AllowClrWrite enough to fill the needs or is something else missing too perhaps?

from jint.

No, for me it is perfectly fine :)

from jint.

Cool, thanks for raising the issue and investigating!

from jint.