Skip to content

11.0 empty string comments #9742

@Maismaus

Description

@Maismaus

Please use the form below, leaving the prefilled data to help us. Thank you.

Page link: 11.0

Document link: 11.0.md

My Issue/Suggestion

I'm confused by these two lines. They seem to contradict each other, and they mention what has changed, but not what the new results would be.

  • We changed string concatenation in expressions for empty/null values. Such values are not anymore concatenated as ’null’. The old behavior can be achieved by using an if-else expression (e.g. 'Value: ' + (if $value != empty then $value else 'null') instead of 'Value: ' + $value).
  • We changed the internal representation in the client of an empty value from an empty string to null. This fixes an issue where empty string attributes become an empty string value when an object is communicated to the client. Due to this change, both MxObject#get and MxObject#set have changed to accept/return null for empty attributes.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions