Timeline for Unique Identifiers for classes - Java with Spring
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 1, 2016 at 19:17 | comment | added | Rahul | Thanks for the responses. Are there any design related flaws with this approach (i.e. maintaining validators in the config) or is there any better,alternative way to achieve the same? | |
| Jul 28, 2016 at 7:54 | comment | added | JDT | I can't imagine any descriptive validator name clashing, but I'm not aware of the domain you are working in so I might be wrong. You might end up with some rather long names to guarantee 'uniqueness' but as long as those names are descriptive length should rarely be an issue. | |
| Jul 28, 2016 at 7:52 | comment | added | JDT | Yeah, well if these 'identifiers' are class names this question would make no sense. It is clearly stated that v1 would be an id and I am making the case for these id's being in a human-understandable format. | |
| S Jul 28, 2016 at 5:54 | history | suggested | Pritam Banerjee | CC BY-SA 3.0 |
Formatted code and grammar
|
| Jul 28, 2016 at 4:28 | comment | added | candied_orange | Yeah, it's called a compiler. These are class names not simply strings. | |
| Jul 28, 2016 at 3:47 | comment | added | Rahul | Thanks for the response! My only concern with that approach is possible duplication / name clash of two different validators. Is there some way to effectively eliminate that? | |
| Jul 27, 2016 at 23:45 | review | Suggested edits | |||
| S Jul 28, 2016 at 5:54 | |||||
| Jul 27, 2016 at 19:00 | history | answered | JDT | CC BY-SA 3.0 |