I wish this were a April Fool's joke, but here we are:
A lot of the issues CTI came back with have to do with the fact that there's no good way for me to determine which apps are and aren't flex. You have to tell by looking at their ASP to know that.
Temporarily, the only apps that are using the functionAppConfig property are flex apps (because they are being created on the new api-version). I doubt that this is going to remain that way forever, but this is a temporary solution for us to add a flex context value.
I'll remove all of this garbo code once the new SDK drops with the required api-version and typing.
I wish this were a April Fool's joke, but here we are:
A lot of the issues CTI came back with have to do with the fact that there's no good way for me to determine which apps are and aren't flex. You have to tell by looking at their ASP to know that.
Temporarily, the only apps that are using the
functionAppConfigproperty are flex apps (because they are being created on the new api-version). I doubt that this is going to remain that way forever, but this is a temporary solution for us to add a flex context value.I'll remove all of this garbo code once the new SDK drops with the required api-version and typing.