ArrayInstance class not opened for extenstions

[xtadex]

While migrating from V2 to V3, I noticed that in V3, the ArrayInstance is not opened for extension (all virtual methods are marked as sealed). I used a virtual method for tracking changes in the array by overriding these methods.

[lahma]

Can you share some code which would show the requirements and use case for you. I'd think Proxy could be an answer to this but I would need more details.

[lahma]

It's just that your implementation looks somewhat redundant now that Jint can expose types like IList in quite logical way. So example code without your custom wrapper and Jint wrapping and showing missing bits would be great.

I'm hoping Jint could cater these interop scenarios without much custom code.

[xtadex]

If Jint can wrap my custom IList, it will be perfect. Then, I can intercept all array updates inside the IList implementation.

Do you think it will work for me?

IList mylist = new DataModelList(); var jsArray = JsValue.FromObject(engine, my);

If the JS script modifies jsArray, I will see all changes immediately in the mylist object. Correct?

[lahma]

This should be the case, but please verify.

[xtadex]

I've checked this approach.
The quick test console app is here https://github.com/xtadex/JintV3Test/blob/main/JintV3Test/Program.cs

It can read/write elements inside of IList<>, but it fails on

• write outside of upper bound (in JS array length adjusted to make write operation successful)
• the length of the underlying array can't be changed by any of operations:
  • set length property
  • calling push()
  • write above upper boundary

[lahma]

Would you like to take a stab to improve the current interop logic? I'm not sure which parts might need a separate interop configuration switch so they wouldn't be surprising.