-
Notifications
You must be signed in to change notification settings - Fork 268
Description
Description
Description
Currently, when a record type (such as ConnectionConfig) is used as a parameter in init methods, the record fields should be expanded into separate, individual fields in the generated UI schema and configuration. This functionality should also apply to remote and resource functions that accept record type parameters.
Current Behavior
When an init method accepts a record type parameter, the entire record is treated as a single field, making it difficult for users to configure individual properties of the record in the Micro Integrator UI.
Example:
public isolated function init(ConnectionConfig config, string serviceUrl = "https://disease.sh") returns error? {
// ...
}In this case, ConnectionConfig should be expanded so that each field in the record becomes a separate configurable field in the UI.
Expected Behavior
Record type parameters in init methods (and also in remote and resource functions) should be expanded into their individual fields, allowing users to configure each field separately in the Micro Integrator UI.
Version
No response