[WTF-2648] Extend pluggable widget API docs for single object datasource#11159
Draft
mlaponder wants to merge 2 commits into
Draft
[WTF-2648] Extend pluggable widget API docs for single object datasource#11159mlaponder wants to merge 2 commits into
mlaponder wants to merge 2 commits into
Conversation
weirdwater
suggested changes
May 13, 2026
| | Web | Context, Microflow, Nanoflow, Listen to widget | | ||
| | Native | Context, Microflow, Nanoflow | | ||
|
|
||
| A single object data source may be linked to [`action`](#action), [`attribute`](#attribute), [`association`](#association), [`expression`](#expression), [`text template`](#texttemplate), and [`widgets`](#widgets) properties using the `dataSource` attribute on those properties. When linked to a single object data source, those properties receive the same types as unlinked properties — there are no list-aware variants: |
Contributor
There was a problem hiding this comment.
To emphasize the differences in behavior between the two types of datasource we may consider adding a combined section about Linking Properties to Datasources. That way we can add a single table with both List Client Types and Single Object Client Types.
For example:
| Property type | List client type | Single object client type |
|---|---|---|
action |
ListActionValue |
ActionValue |
selection |
SelectionSingleValue or SelectionMultiValue |
Not supported |
| ##### Data Source Defaults {#data-source-defaults} | ||
|
|
||
| {{% alert color="info" %}} | ||
| The `defaultType` and `defaultValue` attributes for datasources were introduced in Mendix [10.16](/releasenotes/studio-pro/10.16/). |
Contributor
There was a problem hiding this comment.
We can remove this callout
| | `defaultType` | No | String | Default type for the property, see [Default Data Sources](#data-source-defaults) | | ||
| | `defaultValue` | No | String | Default value for the property, see [Default Data Sources](#data-source-defaults) | | ||
|
|
||
| ##### Data Source Defaults {#data-source-defaults} |
Contributor
There was a problem hiding this comment.
I was expecting to see the limitations for Single Object Datasources here
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Studio Prop 11.11 support for the single object data source API will be introduced, this PR describes the API on that feature.