Repository navigation
refactor: Extract common code from responders into EntityAndClassIriS… - #2348
Conversation
Codecov ReportBase: 86.68% // Head: 86.37% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #2348 +/- ##
==========================================
- Coverage 86.68% 86.37% -0.32%
==========================================
Files 250 268 +18
Lines 28252 28317 +65
==========================================
- Hits 24490 24458 -32
- Misses 3762 3859 +97
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
234ecd2 to
3c1d44d
Compare
mpro7
left a comment
There was a problem hiding this comment.
Overall looks good. There are few typos - see my comments/suggestions. Wouldn't also make sense to write some unit tests for stuff you have moved to separated services?
In general I agree that new code should be covered with unit tests. I will look into if I can improve the coverage. However, I will have to look into if testing the |
irinaschubert
left a comment
There was a problem hiding this comment.
LGTM, just some suggestions regarding documentation / naming. In general, I agree with Marcin that we should have tests - if possible.
mpro7
left a comment
There was a problem hiding this comment.
Just found one minor thing while you were broadcasting.
5acf8c1 to
1a8daea
Compare
…idge and ActorDeps * Add zio-mock dependency to test dependencies * Extract EntityAndClassIriService * Introduce ActorDeps * Introduce ActorToZioBridge * Remove methods on abstract Responder and use iriService in Responder directly * Remove commented out code * Move handleUnexpectedMessage method into Responder and make protected * Expose ProjectsResponder as ProjectsService to ProjectRouteZ * Add scaladoc * Formatting
1a8daea to
c3da43a
Compare
Pull Request Checklist
Task Description/Number
ProjectsAdminServiceas at first a wrapper around its own instances of theProjectsResponderADMexposing the method used in the zio http routeEntityAndClassIriServiceas dedicated service allowing for breaking up the inheritance hierachyActorDepsas a zio layer - a class encapsulating all Akka dependencies necessary to interact with the [[org.knora.webapi.core.actors.RoutingActor]] aka. "appActor"akka.pattern.askinto the zio worldzio-mockdependency to test dependenciesResponderand useEntityAndClassIriServicehandleUnexpectedMessagemethod into Responder and make protectedProjectsServicetoProjectRouteZBasic Requirements
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR change client-test-data?