5
votes
Is it ok to extend utilities?
I don't think there's any justification for extending a util class like that - or even if extending has any technical meaning for a static class with static utils.
Let's say you do create your own ...
- 9,500
3
votes
Exposing dependencies results in "fat" constructor. What should you do next?
You seem to be injecting repositories in what appears to be a frontend component. That suggest that the responsibility of your "dialog" component is much, much deeper than what a "...
- 54.8k
2
votes
OOP Design of a Mathematical Group
A group is a triple of a set, an associative binary operation, and the identity element of that binary operation, with the requirement that every element have an inverse.
The element of one group is ...
- 11.5k
2
votes
Accepted
Abstraction for user notification
Let me restate your problem, so I can describe my guess about where the core problem is located.
Your idea is to let the database layer return some object ("Notification") about the last ...
- 211k
2
votes
Should everything be buildable?
This might be an XY problem. Making things "buildable" isn't the issue. All those optional constructor parameters are the real problem. Lumping a builder on top of this mess only adds a ...
- 40.7k
1
vote
Abstraction for user notification
The notification and feedback request are two different things. I'd recommend to keep the separated - especially when 90% of time you need only one of them. Therefore:
/** Simple tool to notify user. *...
- 119
Only top scored, non community-wiki answers of a minimum length are eligible