My understanding is that when retrieving values through the Content Delivery API, it is merely exposing the values for the content types as they exisit in the database, and not run through the getters of the content types. With the current state of the Content Delivery API, one would have to express this logic in a custom ContentResultService to achieve the same result.
This feature would be much appreciated as it a more scalable solution than relying on custom ContentResultService implementations.
Hi,
It would be great if the Content Delivery API supported taking account for logic expressed in getters for properties in content types, as described in this forum post: https://world.episerver.com//forum/developer-forum/-Episerver-75-CMS/Thread-Container/2019/8/content-delivery-api-exposing-derived-properties/
My understanding is that when retrieving values through the Content Delivery API, it is merely exposing the values for the content types as they exisit in the database, and not run through the getters of the content types. With the current state of the Content Delivery API, one would have to express this logic in a custom ContentResultService to achieve the same result.
This feature would be much appreciated as it a more scalable solution than relying on custom ContentResultService implementations.
Thanks,
Thomas