sdk: Disallow invalid types in MultiLanguage objects - #431
Merged
Conversation
ZANDx1
force-pushed
the
MultiLangTyping
branch
from
November 18, 2025 08:27
b0e223a to
23c1049
Compare
ZANDx1
force-pushed
the
MultiLangTyping
branch
from
November 18, 2025 08:44
23c1049 to
aa532f3
Compare
zrgt
requested changes
Nov 20, 2025
zrgt
requested changes
Nov 24, 2025
Contributor
|
@ZANDx1 please implement the same logic for |
ZANDx1
force-pushed
the
MultiLangTyping
branch
from
December 4, 2025 13:39
4cfda09 to
2a6fc94
Compare
Merged
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
3 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.
Previously, multilingual fields (
display_name,description,MultiLanguageProperty.value) could be assigned invalid types, leading to inconsistentand sometimes invalid JSON/XML serialization.
As a result, this behavior could cause interoperability issues.
The AAS specification requires these fields to be of type
LangStringSet / MultiLanguageTextType. This requirement is nowenforced to ensure spec-compliant serialization.
Fixes #416