Currently planned for the next semester (April 2020) - please note that actual delivery dates can change .
hemant
Basic font and style alignment for the test harness is complete .
We are working on the PCF controls theming and these capabilities will be added to the test harness too as they are released.
hemant
The bug is resolved and changes should be available in production .
hemant
For dataset type components, you can load a CSV file with test data. You manually create or export in .csv format directly from your environment.
You can acheive the same by using type ‘enum’ as following -
A sample property l
<property name="EnableFiltering" display-name-key="CC_Allow_Filtering" description-key="CC_Allow_Filtering_Desc" usage="input" of-type="Enum" required="false" hidden="true">
<value name="Yes" display-name-key="CC_Enable_Filtering" description-key="CC_Enable_Filtering_Desc">yes</value>
<value name="No" display-name-key="CC_Disable_Filtering" description-key="CC_Disable_Filtering_Desc" default="true">no</value>
</property>
I will mark the idea as under review and not resolved so that we can see if there is interest inmaking this first class.
Already in experimental preview ; https://aka.ms/PCFCanvasBlog
These options are added to the test harness. There is some future work to show the optimized rendering but since the control viewport is not known (entire screen is not control) we are evalauting options to make it configurable.
Controls at a level below the expressions, formulas and Client Apis.
Canvas PCF support is already in the preview and we have expressions supported there for PCF.
Going fwd we will have the custom pages in the model apps which will support expressions on the model PCF.
Also there is work in progress to enable PCFs to delcare the events inthe properties like onClick and expose these to formulas .
Please let me know if I need to repoen this to to track any specific ask as the idea is really broad. Or please log a new one
hemant
Client APIs for the control work irrespective of the PCF or the native PCF OOB control. We are looking into makeing the controls more expression aware and also add eventing in future. ClientAPIs support expansion is not planned at this point.
Hemant
This is the control implementation ask which can be acheived by buiding the control with speciel logic and have these contrains as part of configuration.
Custom property editor and way to enable the control creators to define the authoring time expereince is important , esp in the canvas apps targeting citizen developers. We have done some engineering investments to let control makers define the right properties authoring experiences and are right now being utilized by 1st party PCF controls like AI builder and Power MR. This will be made available externally in future releases.
Please see release wave 2 plan below -
https://docs.microsoft.com/en-us/power-platform-release-plan/2020wave2/power-apps/power-apps-compone...