-
Notifications
You must be signed in to change notification settings - Fork 13
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
[SDFAB-186] Up4Service to expose network-level API #153
Conversation
Codecov Report
@@ Coverage Diff @@
## master #153 +/- ##
============================================
- Coverage 57.99% 56.95% -1.05%
Complexity 204 204
============================================
Files 16 16
Lines 2183 2223 +40
Branches 259 260 +1
============================================
Hits 1266 1266
- Misses 798 838 +40
Partials 119 119
Continue to review full report at Codecov.
|
@ccascone @pierventre |
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. Left just a minor comment. Feel free to merge after fixing that (I'm giving you write permissions, so you should also be able to add reviewers).
app/app/src/main/java/org/omecproject/up4/impl/Up4DeviceManager.java
Outdated
Show resolved
Hide resolved
Refactor Up4Service to expose UPF network level API. The Up4Service implementation is in charge of selecting the UPF programmable.
@ccascone I believe I don't have write permission. Anyway, I rebased and now it can be merged. |
Waiting on @pierventre review before merging. |
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.
Mostly clarifications
Refactor Up4Service to expose UPF network-level API.
The Up4Service implementation is in charge of selecting the right UPF programmable.