-
The only failures I’m aware of are the ones that test the native JSONItem, and are meant to show the limitations of that class, and let us know when or if they are fixed. Are you seeing others?
-
Yes, it seems I could have done that. At the time I thought I’d be shadowing properties that should not be shadowed, but a quick test shows that I can probably eliminate those properties. I’ll consider that for some future version, but the issue hasn’t really come up. (Keep in mind that this class is many years old now.)
Switching your project over to my class is just a matter of doing a find/replace of JSONItem -> JSONItem_MTC. There shouldn’t be any other code changes.
Moving forward, I’d expect people to use the new ParseJSON and GenerateJSON native methods as they are significantly faster.
You’re welcome to do a pull request against my develop branch and I’ll consider your changes.