You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this iteration we don't have to validate that the attributes of the connection match with the declarations in the connection descriptor, so we don't need to add support for installing contributions of type connection. This will allow us to quickly provide basic support for connections.
We will mostly just update the mapper so if a contrib has a setting of type connection it won’t use the mapping wrapper. Also we will collect the connections refs to add them to the imports of the app during the export process.
Mapping of connections
Currently when the mapper UI infers that the user provided an value of type object it wraps the object with an attribute mapping. In order to support connections the mapper will need to first check if the attribute is of type connection and if it is then it should just store the object value provided by the user, for other types the old behavior should not be changed.
Is your feature request related to a problem? Please describe.
This is part of #1330 Connections support
This a feature request for supporting in-line connections
Example of inline connection in app.json
To Do
ref
s of the used connections should be part of theimports
of the appDetails of changes
For this iteration we don't have to validate that the attributes of the connection match with the declarations in the connection descriptor, so we don't need to add support for installing contributions of type
connection
. This will allow us to quickly provide basic support for connections.We will mostly just update the mapper so if a contrib has a setting of type
connection
it won’t use the mapping wrapper. Also we will collect the connections refs to add them to theimports
of the app during the export process.Mapping of connections
Currently when the mapper UI infers that the user provided an value of type object it wraps the object with an attribute
mapping
. In order to support connections the mapper will need to first check if the attribute is of typeconnection
and if it is then it should just store the object value provided by the user, for other types the old behavior should not be changed.Examples:
❌ Wrong if setting
foo
has data typeconnection
✅ Correct if setting
foo
has data typeconnection
Questions
connection
supported anywhere a data type can be used? If so:connection
supported in the input of an activity/stage? If so:The text was updated successfully, but these errors were encountered: