Accessing internal function using .get

[Shashwat]

This sample works till 2022 R3 SP1: https://dojo.telerik.com/EqaQuWAn

Some parts of our code has observable objects accessing functions using `get('functionName()')` format.

This no longer works since 2023 R1 and I cannot find any details about it in the change log. I don't know how to access docs for older versions either, but I do remember the docs suggesting this function access pattern.

Could you please help me find either the change log or older docs?

[Shashwat]

More context about this (recollecting from memory): this was suggested for the usecase where you have a dependency like:

computed2 depends on computed1 depends on field1

[Shashwat]

Another example that works before 2023 R1, but throws error in console after that: https://dojo.telerik.com/EqaQuWAn

These are some code snippets that are breaking after we upgrade, and needed to understand if there's some changelog to narrow down the impact.

[Martin]

Hello, Shashwat,

Thank you for the provided examples.

Apparently the example is affected by selection defined as null. If you comment out the field, or set it as undefined, the example appears to be working. Here is the modified example with the latest version.

Regarding the documentation, we do not keep an older state.

I hope the above information will be useful.

Regards,
Martin
Progress Telerik

[Shashwat]

hi Martin,

We have a medium-large app using mvvm extensively, and it throws after upgrade. I was asking this question to assess impact of upgrading an already functioning application as opposed to fixing this particular issue.

We did ensure to follow the docs and not use any internal APIs, so were not expecting such issues based on the changelog. This leaves us having to test a pretty large area without understanding what aspects are impacted.

So, is it possible to understand what other areas of "mvvm" have changed between the two releases, as I am having trouble finding anything about it in the upgrade/changelog. This is so we can focus on testing those cases first.

Hope this clarifies where I'm coming from.

Regards,

 

 

[Martin]

Hello, Shashwat,

Every major or breaking change we make to our components are listed in our Backwards Compatibility articles. Any other changes that are affecting a user's project are most commonly made unintentionally. That is why we are at your disposal to help you in such cases.