# Issue with .remove on array **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [June 1, 2023, 7:35pm UTC](https://forum.inductiveautomation.com/t/issue-with-remove-on-array/74464 "2023-06-01T19:35:24Z")\ **Posts on this page:** 1\ **Showing post:** 22
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [June 7, 2023, 7:27pm UTC](https://forum.inductiveautomation.com/t/issue-with-remove-on-array/74464/22 "2023-06-07T19:27:34Z")
> [@paul-griffith](#): > > I think there's an existing ticket to further improve the wrapper classes that should cover this case; they just need to be smarter about their own equality. I feel like this duck analogy is in order again... > [@Is it possible to pass variable from gateway scope to client scope?](https://forum.inductiveautomation.com/t/is-it-possible-to-pass-variable-from-gateway-scope-to-client-scope/45008/21): > > One of the datatypes somewhere in the structure you’re passing into jsonEncode is more than likely not a real dict/list type and jsonEncode barfs on them. There was a [recent forum discussion](http://forum.inductiveautomation.com/t/jsonencode-issue/44603) about this failure symptom. This is a problem with [duck-typing](https://en.wikipedia.org/wiki/Duck_typing) languages in general. As I put it to my colleague, something in the structure can walk like a duck and quack like a duck, and has been passing as a duck for a very long time, but when I asked it to lay an egg it fell over and died. --- _[View the full topic](https://forum.inductiveautomation.com/t/issue-with-remove-on-array/74464)._