-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Reduce exports from SotoSignerV4 #567
Conversation
Codecov Report
@@ Coverage Diff @@
## 7.x.x #567 +/- ##
=======================================
Coverage 78.87% 78.87%
=======================================
Files 71 71
Lines 6292 6292
=======================================
Hits 4963 4963
Misses 1329 1329 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Reducing exports is always good - is there any reason why these are needed at all for v7?
I think it is a good idea to export the symbols my public APIs use. Makes it easier for the end user. |
Oh completely agree - are things like ByteBuffer going to be part of the public API though? (This is a more general question as opposed to being specifically about this PR, I know removing all the future APIs is a multi step process) |
ByteBuffer is part of the public API. I don't think that is going to change. Unless we get the bag of bytes type in the sodlib |
🤦♂️ travel brain getting futures and byte buffers mixed up |
No description provided.