Timeline for Injecting stereotypical role implementations by IoC container
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2017 at 17:37 | comment | added | Dmitry Nogin | I have explicitly recommended myself to use Scala as an example of common sense ;) | |
| Jun 6, 2017 at 17:30 | comment | added | Der Kommissar | @DmitryNogin Jon Skeet recommends always including explicit access modifiers because it shows you explicitly chose the modifier. ;) | |
| Jun 6, 2017 at 17:25 | comment | added | Dmitry Nogin | 3) Agree, Query.Result.Value is more readable. 4) I have never been changing how things been validated. Really :) It means that I have different query or, at least, different query parameter values – so it works fine. The same time, I have a lot of query reuse, so this what needs to be syntactically cheap. Multiple validators are totally OK – they all cooperate on the subject as intended – it is an extension point. And, in year 2017, I use registration by convention, so it is hardly to be an issue :) | |
| Jun 6, 2017 at 17:25 | comment | added | Dmitry Nogin |
1) private - Common, it is year 2017. We do not write code which is not necessary to write anymore. Actually, Principles behind the Agile Manifesto: “Simplicity--the art of maximizing the amount of work not done--is essential” (c) 2001 :) 2) It is a way easy to refactor by extracting methods when there are no local variables (Refactoring: Improving the Design of Existing Code by Martin Fowler). One could say that these is how functional code looks like – when one does write code, it is more generally condensed than it used to be in days of old – in imperative era.
|
|
| Jun 6, 2017 at 13:52 | history | answered | Der Kommissar | CC BY-SA 3.0 |