added --preserve-case

[TJKoury]

Summary

• Add preserve-case coverage across the language test harnesses (C++, Go, PHP, Python, TypeScript/JavaScript, Java, Dart, Rust, JSON Schema)
• Extend each suite to regenerate code with and without --preserve-case, run the matching tests, and clean up generated artifacts
• Add helper utilities (e.g., TypeScript aliasing, Java JUnit runner, JSON Schema verifier)

[aardappel]

Please note what I said in the thread leading up to this, in particular this comment: #7111 (comment)

[TJKoury]

Please note what I said in the thread leading up to this, in particular this comment: #7111 (comment)

Understood, please refer to my response here.

If you think this is too niche to include, or too much to review, I will maintain my fork separately for my own requirements.

If the issue is the tests, I can remove those and maintain them separately.

Unfortunately, property name mangling is manually inserted into the code generators, completely bypassing the idlnamer system. After three iterations this is the least invasive way I can think of to do it.

Thanks for your time, please let me know soonest.

[aardappel]

That may be the best solution, as getting this in a mergable shape may be too much work that is not worth your time.

It needs to be a minimal change. It currently hard to review because there is a lot going on.

We certainly don't want to fork all of our tests for the sake of this feature. But even removing that it may still be too unwieldy. The need for these compatibility functions seems to make it worse.

[TJKoury]

Understood. If there’s a more minimal way to do it I would certainly welcome feedback.

The tests are not forked, new tests were added that are mirrored versions of the current tests. Of course, this means changing one leads to changing both.

I will maintain a fork, and will always welcome future collaboration if it makes sense to roll this feature in at a later date.

[TJKoury]

I am fixing the CI issues locally, standby for cleanup.

[TJKoury]

@aardappel @dbaileychess I have not tried running the CI on an Windows VM, however I think I fixed all the other issues.

Let me know if you are still considering this, or if we should just close it out. Will maintain this feature on my fork.

[aardappel]

I don't think anything has changed about my evaluation(s) above.