Timeline for In a Spring Boot Project, would you use interfaces for entities or not?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2019 at 14:10 | review | Close votes | |||
| Sep 5, 2019 at 3:05 | |||||
| Aug 21, 2019 at 10:27 | history | edited | gnat | CC BY-SA 4.0 |
typo in title corrected
|
| Aug 21, 2019 at 10:24 | vote | accept | Tom | ||
| Aug 21, 2019 at 10:23 | vote | accept | Tom | ||
| Aug 21, 2019 at 10:23 | |||||
| Aug 21, 2019 at 10:15 | answer | added | Kayaman | timeline score: 1 | |
| Aug 21, 2019 at 9:54 | history | edited | Tom |
edited tags
|
|
| Aug 21, 2019 at 9:45 | comment | added | Tom | Do you see any reason why they did that in the broadleaf project than? I am very curious, because I did see that idiom actually a couple of times already, for example in liferay project too. | |
| Aug 21, 2019 at 9:42 | comment | added | Kayaman | If you think it will help you in the future, go for it. I don't really see the point of an additional abstraction layer there. In fact I'd say this makes it a bit too easy to pass entities around, instead of using dtos/domain objects. Would have to study the architecture of that project to see how it uses them, but I've never made interfaces for entities, and I doubt I'll start now. | |
| Aug 21, 2019 at 9:23 | comment | added | Tom | Well, I already had quite some work with refactoring and bugfixing and I think that future debugging/refactoring would benefit from that. | |
| Aug 21, 2019 at 8:43 | comment | added | Kayaman | As a quick answer, refer to the YAGNI principle. You've noticed that it's not a common idiom, so it's probably not essential for your architecture. | |
| Aug 21, 2019 at 8:25 | review | First posts | |||
| Aug 21, 2019 at 13:50 | |||||
| Aug 21, 2019 at 8:22 | history | asked | Tom | CC BY-SA 4.0 |