
Announcements
For those of use restricted from accessing the environment and using vscode to author components, a mini code editor would be productively useful as well as investigating/understanding what is going on under the covers when things go awry either with our coding or with the environment.
What I suggest is that when editing a custom component an option for "code editor" is displayed which renders the underlying json/yaml/etc to friendly pseudo code that can be edited using a simple text editor (without intellisense being supported initially) and when saved is deconstructed, and internal file(s) updated --> display updated. This would also reduce the app studio workload tracking everything as code changes are made realtime.
eg. first line defines the custom property, its type, direction (I/O), parameters, and data type, with following lines defining other properties, default values, and the formula.
as an explicit eg. CustomFunc with parameters p1, p2, and optional parameters p3 and p4
//Compiler error messages are generated when this file was generated
//First line must start with #Output Function,#Input Function, #Output Data, #Input Data, #Event, or #Action
#Output Function CustomFunc(p1 as Record, p2 as Number ,Optional p3 as Text, Optional p4 as Num) as Number
//Definition: Parameter p4 unrecognised type
DisplayName: ....
Description: ...
RaiseOnReset:false
p1:Defaults(myTable)
//p1 as Record: myTable is not recognised
p2:{a:1}
//p2: Defined type and default value type mismatch
p3:"stuff"
CustomFunc: Switch(p3,"a",1,"b",2,99))
//CustomFunc: Unmatched brackets (extra closing parenthesis)
PAC cli unpack/pack is the only available option today. We'd love to have a better native file format that could be supported in a variety of ways like what you describe but that is not on the roadmap at the moment, unfortunately.