-
Notifications
You must be signed in to change notification settings - Fork 1
refactor: problem bound structure #143
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
base: develop
Are you sure you want to change the base?
Conversation
| } | ||
|
|
||
| public void compareBound() { | ||
| if (this.solution == null) { |
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 we outsource this check to BoundWithInfo or ComparisonDto? It would be nice if we would have an indicator by a method call from the class which signalizes that the bound may not be set - isBoundSet() for instance?
| import edu.kit.provideq.toolbox.BoundWithInfo; | ||
| import edu.kit.provideq.toolbox.Solution; | ||
|
|
||
| public record ComparisonDto(float comparison, BoundWithInfo bound, Solution<?> solution) { |
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.
It would be nice if you included an JavaDoc for this class
Introduced a hasBound() method in ComparisonDto to check for the presence of a bound. Updated Problem to use hasBound() instead of directly checking for null
…/ProvideQ/toolbox-server into refactor/problem-bound-structure
|



No description provided.