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
refactor: Move project related value objects to admin.domain.model package and cleanup code #2923
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2923 +/- ##
===========================================
+ Coverage 11.68% 88.23% +76.54%
===========================================
Files 251 248 -3
Lines 23065 22989 -76
===========================================
+ Hits 2695 20284 +17589
+ Misses 20370 2705 -17665
☔ View full report in Codecov by Sentry. |
ffc434e
to
2378205
Compare
eefd8e4
to
7b0becf
Compare
0139859
to
8338fee
Compare
8338fee
to
e9b344d
Compare
e9b344d
to
ab84069
Compare
… with private constructor pattern https://tuleism.github.io/blog/2020/scala-smart-constructors/
Remove unused scala options
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.
Looks good, apart of places where I suggest changes.
Also general question, why to not keep store error messages in object vals instead of keep repeating them?
The error message is only used once in production code and is encapsulated in the function returning the error. This approach keeps it close to the actual usage of the code responsible for validation. I have introduced redundancy in the test to ensure that a change in the production code will cause the test to fail if we unintentionally alter the desired return value. Previously, one could change any of the |
Pull Request Checklist
Task Description/Number
from 2.13.2, the
sealed abstract case class private
can be reduced by enabling-Xsource:3
. From scala/scala#7702:see also https://tuleism.github.io/blog/2020/scala-smart-constructors/
This way it is also possible to reduce boxing for value classes which can extend
AnyVal
.However this PR does not include the activation of that flag as some existing code needs to be updated as well, this is done in #2924
PR Type
Basic requirements for bug fixes and features
Does this PR introduce a breaking change?
Does this PR change client-test-data?