Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PubSub] BuiltInType.Null array handling inconsistency #2522

Open
1 of 5 tasks
etoensfeldt opened this issue Feb 15, 2024 · 0 comments
Open
1 of 5 tasks

[PubSub] BuiltInType.Null array handling inconsistency #2522

etoensfeldt opened this issue Feb 15, 2024 · 0 comments

Comments

@etoensfeldt
Copy link

Type of issue

  • Bug
  • Enhancement
  • Compliance
  • Question
  • Help wanted

Current Behavior

Currently ValueRank for BuiltInType.Null fields gets ignored when decoding mqtt messages:

However sending a data for a BuiltInType.Null field will keep the data and therefore ValueRank intact, instead of sending just null over MQTT. (I haven't checked if this is also the case for UADP)

This strikes me a bit inconsistant, is this intentional?

Expected Behavior

I'd expect when sending an array with two null elements to also be able to receive an (object-)array with two null elements. The sending side currently works, however the received UaNetworkMessage only contains a null scalar.

The usefulness of this may arguably be low, but it would offer more consistent behavior and not lose the sent information about array dimensions.

Steps To Reproduce

No response

Environment

- Nuget Version: 1.5.373.121
- Component: Opc.Ua.PubSub
- Server: Mqtt (HiveMQ)

Anything else?

No response

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

No branches or pull requests

2 participants