-
Notifications
You must be signed in to change notification settings - Fork 79
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
update opcua modules - remove unnecessary data transformation #1072
Conversation
2394ae4
to
8ee12eb
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1072 +/- ##
=======================================
Coverage 75.67% 75.67%
=======================================
Files 80 80
Lines 16159 16159
Branches 1519 1519
=======================================
Hits 12228 12228
Misses 3889 3889
Partials 42 42
☔ View full report in Codecov by Sentry. |
8ee12eb
to
4aba543
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you try to avoid those changes in the package-lock? I'm afraid they will randomly appear in the future if we do not fix them now.
7e3bcea
to
be0c3c8
Compare
be0c3c8
to
14a85bf
Compare
FYI: I created a new node-wot release with newer dependencies. Maybe you can simply align (by merging in master) the versions there... not sure if it helps |
To bring this PR forward I plan to split this PR in several PRs to fix/update each part separately. |
I opened 3 follow-up PRs:
Once they are merged we can close this one... |
* chore(binding-opcua): improve/stabilize tests see #1072 * fix typo Co-authored-by: Jan Romann <jan.romann@uni-bremen.de> --------- Co-authored-by: Jan Romann <jan.romann@uni-bremen.de>
Is this really necessary ? At the end the code will be idential in the repo |
I see some conflits, I'll rebase. |
3a39b66
to
e246446
Compare
Co-authored-by: Jan Romann <jan.romann@uni-bremen.de>
8e27f3f
to
ba3dcf4
Compare
We (and most other projects) have the policy to create one PR per issue/change. Putting a lot of stuff in 1 PR is not useful and makes it
I hope you can see our rational... By now the other PRs have been merged and I will close this one. Thanks for your contribution! |
No description provided.