Skip to content

Use only expression mode for maps, lists and tuples#656

Merged
LakshanWeerasinghe merged 11 commits intoballerina-platform:hotfix-1.5.1from
LakshanWeerasinghe:fix-expr-set
Jan 23, 2026
Merged

Use only expression mode for maps, lists and tuples#656
LakshanWeerasinghe merged 11 commits intoballerina-platform:hotfix-1.5.1from
LakshanWeerasinghe:fix-expr-set

Conversation

@LakshanWeerasinghe
Copy link
Contributor

@LakshanWeerasinghe LakshanWeerasinghe commented Jan 23, 2026

Purpose

$subject

Fixes Part Of: wso2/product-ballerina-integrator#2310

There is a limitation of serializing and deserializing map and list values between expression mode and specific mode for the type in the UI. Until we find a way to resolve this limitation from the UI side we are going to only use expression mode for maps, lists and tuples.

Screen.Recording.2026-01-23.at.15.59.52.mov

@LakshanWeerasinghe LakshanWeerasinghe merged commit fb677a9 into ballerina-platform:hotfix-1.5.1 Jan 23, 2026
3 checks passed
Comment on lines -636 to -642
if (paramType.get().typeKind() == TypeDescKind.MAP) {
matchingValueType = ValueType.MAPPING_EXPRESSION;
// convert string to a Map<String, Object>
Map<String, Object> mapValue = CommonUtils.convertMappingExprToMap(
(MappingConstructorExpressionNode) value);
value(mapValue);
} else if (paramType.get().typeKind() == TypeDescKind.RECORD) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the change is temporary, we should ideally add a TODO comment instead of removing the entire code block. Better if we can create an issue for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants