feat(dts-generator): add TypedJSONModel

[martinbroede]

Add the type definitions for the TypedJSONModel and adapt the generator to insert them to the core d.ts file.

Related to #509 – thanks for your submission, @akudev !
I added tests for TypedJSONModel, which can be executed separately via npm run test:typed-json-model, so they can be added to CI when appropriate.

[cla-assistant]

All committers have signed the CLA.

[akudev]

rebase now against the primary error in node 18 and update the expected test result in openui5-snapshot-test with "npm run re-generate"

[akudev]

Related to #509 – thanks for your submission, @akudev !

Ah, that was just putting your code to the right places - thanks a lot for the implementation, it's great to get this in!

In addition to the comments above, as I told you, please document what to do when a fix is needed, esp. how to update the code in the dts-generator. My prior mail had the description how I split type definitions and implementation. For a small fix or extension you'd probably just apply the changes to what we already have in the dts-generator and in the OpenUI5 repo, not do the full splitting exercise again.

Also, we need some documentation for users of the TJM. We only have the JSDoc in the types themselves (good but hard to discover when you don't know the feature) and the sample app deep inside this repo. If you write up some markdown, we can find a good place. E.g. in the gh-pages branch of this repo, where we can get it in immediately (and where you can develop the docu as PR).
Ultimately, however, it should be in the UI5 documentation, ideally in the same release when we enable it and when it would be noted in the "What's new section" (need to trigger this as well!). Probably as a section or sub-page of https://sdk.openui5.org/topic/96804e3315ff440aa0a50fd290805116#loio96804e3315ff440aa0a50fd290805116
Doesn't need to be much.

That place would also be a good one to mention the limitations. Including the relatively esoteric technical ones within the model you already described, but more importantly the real-life ones outside the TJM itself which are more likely to be seen by users, like that in XMLView bindings there is of course no type safety provided by using a typed model (so you can still bind to non-existing properties) etc.

[akudev]

Alright, this looks good to me now. Only the version dependency of adding the TJM types to the dts file is missing.

@codeworrior , @petermuessig if you want to have a look as well...

[petermuessig]

AFAICS and besides the already raised comments (Andreas, Frank) it looks good. Can't wait to see it live...

[martinbroede]

@akudev wrote:

Also, we need some documentation for users of the TJM. We only have the JSDoc in the types themselves (good but hard to discover when you don't know the feature) and the sample app deep inside this repo. If you write up some markdown, we can find a good place. E.g. in the gh-pages branch of this repo, where we can get it in immediately (and where you can develop the docu as PR). Ultimately, however, it should be in the UI5 documentation, ideally in the same release when we enable it and when it would be noted in the "What's new section" (need to trigger this as well!). Probably as a section or sub-page of https://sdk.openui5.org/topic/96804e3315ff440aa0a50fd290805116#loio96804e3315ff440aa0a50fd290805116 Doesn't need to be much.

I've just opened PR #605 in the ui5-docs repo concerning the UI5 Demo Kit and the WN-Section.