Timeline for Should I use custom entity types and custom fields to represent complex data types, or is it better to stick with fields and field collections?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2019 at 17:43 | comment | added | 4uk4 | @greendemiurge, this was asked before, see drupal.stackexchange.com/questions/22586/… and drupal.stackexchange.com/questions/197669/… | |
| Feb 26, 2019 at 17:06 | comment | added | greendemiurge | Thanks to you both for weighing in. Leymannx, I guess I'm most interested in if someone can spot big pitfalls that I'm not aware of, so it helps just to know these are all valid. 4k4, do you have any hints where I can find docs on what benefitsi leave on the table if I use a custom entity? | |
| Feb 26, 2019 at 16:55 | review | Close votes | |||
| Mar 15, 2019 at 3:05 | |||||
| Feb 26, 2019 at 16:45 | comment | added | 4uk4 | In D8 compound fields are the most efficient option, too. Since it is easy to generate a custom field type plugin you don't need a contrib module, only Drupal Console, which you probably already use to generate custom entities. For nodes vs. custom entities there is no clear answer. If you need the features nodes provide, build content types, otherwise build custom entities. | |
| Feb 26, 2019 at 16:38 | comment | added | norman.lol | Oh man, you really took some effort to write down your question(s). But honestly, it's simply an opinion-based issue. It's absolutely up to you. You can ask this question 10 dev and probably get 10 different answers. | |
| Feb 26, 2019 at 16:12 | history | asked | greendemiurge | CC BY-SA 4.0 |