Skip to content

Conversation

@1nf0rmagician
Copy link
Member

Fix missing localization for ProcessDataListenerConfig

(cherry picked from commit 28c1c0c2d1ffce75cd111d740c2834d9762377ec)

PHOENIXCONTACT/MORYX-Factory#116

@1nf0rmagician 1nf0rmagician self-assigned this Sep 25, 2025
@1nf0rmagician 1nf0rmagician added this to the Framework 10.0.0 milestone Sep 25, 2025
seveneleven
seveneleven previously approved these changes Oct 7, 2025
…ENIXCONTACT/fix/missing-localization-for-processdatalistenerconfig

Fix missing localization for `ProcessDataListenerConfig`

(cherry picked from commit 28c1c0c2d1ffce75cd111d740c2834d9762377ec)
@1nf0rmagician 1nf0rmagician force-pushed the port/missing-localization-for-processdatalistenerconfig-to-future branch from bef6468 to 4f3149e Compare October 9, 2025 05:45
@1nf0rmagician 1nf0rmagician merged commit 018c93b into future Oct 10, 2025
4 checks passed
@1nf0rmagician 1nf0rmagician deleted the port/missing-localization-for-processdatalistenerconfig-to-future branch October 10, 2025 04:15
/// </summary>
[DataMember]
[Description("Unique Name of the Listener")]
[Display(Name = nameof(Strings.LISTENERNAME), Description = nameof(Strings.LISTENERNAME_DESCRIPTION), ResourceType = typeof(Strings))]
Copy link
Member

Choose a reason for hiding this comment

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

Naming convention of the resource keys is <ClassName>_<PropertyName>_DisplayName or <ClassName>_<PropertyName>_Description @DosenSuppe could you fix that in MORYX-Factory and then update the port?

Sample for here: ProcessDataListenerConfig_ListenerName_DisplayName.

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.

4 participants