5 ms·
Where are you seeing that it's a standard code format? I've skimmed this: https://powerapps.microsoft.com/en-us/blog/what-is-microsoft-power-fx/ https://powera
by mgummelt 5y ago
Where are you seeing that it's a standard code format? I've skimmed this: https://powerapps.microsoft.com/en-us/blog/what-is-microsoft-power-fx/ https://powerapps.microsoft.com/en-us/blog/what-is-microsoft... and it seems that it's just a simple expression language, not a standard format that an entire PowerApps app would compile down to.
- hudgeon 5y agoHmmm. Good question. I was using standard format to mean two things: 1. Common code format across the Power platform, and 2. the branding MS was using to describe everything that would be put under source control. I have some doubts about whether the second point is true. This article (https://docs.microsoft.com/en-us/power-platform/power-fx/overview https://docs.microsoft.com/en-us/power-platform/power-fx/ove...) discuss PowerFX stored as YAML files under source control. And this article which predates the PowerFX announcement (https://powerapps.microsoft.com/en-us/blog/source-code-files-for-canvas-apps/ https://powerapps.microsoft.com/en-us/blog/source-code-files...) discusses UI YAML files under source control. But nowhere does it say that they are branding the UI YAML files under the PowerFX moniker.
- mgummelt 5y agoEven then, if the YAML files can only be interpreted by Power Apps, then they can't be portably deployed.