Repository navigation
Add Testcase for EncodeDataValueWithoutValueProperty - #3579
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3579 +/- ##
===========================================
+ Coverage 51.86% 66.11% +14.24%
===========================================
Files 370 459 +89
Lines 78618 97715 +19097
Branches 13650 16375 +2725
===========================================
+ Hits 40779 64601 +23822
+ Misses 33705 28037 -5668
- Partials 4134 5077 +943 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@KircMax in current master i think it the audit event fixed already |
|
@romanett I synched the fork today before I created that branch - it also shows "up to date with master": |
romanett
left a comment
There was a problem hiding this comment.
As this Library is like a reference implementation I dont like this change.
You can leave the test and maybe change the AdjustExpectedBoundaryValues to handle this statement in the spec:
https://reference.opcfoundation.org/Core/Part6/v105/docs/5.2.2.17
|
@romanett should I also adjust the other encoders accordingly? |
romanett
left a comment
There was a problem hiding this comment.
Sorry I had some issue wrapping my head around. With this Change still the Server would not encode Messages like stated in the spec. This is not right.
) * add EncodeDataValueWithoutValueProperty * adjust de and encoder for datavalue -> always handle sourcepico, etc. * extend EncodeDataValueWithoutValueProperty test * nullhandling is needed * keep declaration as it was * keep binarydecoder, adjust the test case * add spec. comment * keep binaryencoder



Proposed changes
Describe the changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Related Issues
Types of changes
What types of changes does your code introduce?
Put an
xin the boxes that apply. You can also fill these out after creating the PR.Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...