With the introduction of groupable config entities, it no longer makes sense to refer to grouped entities as "group content" as this leaves config out of the equation. Let's fix that by renaming these parts of the API to mention "relationship".

CommentFileSizeAuthor
#4 group-3293038-4.patch188.59 KBkristiaanvandeneynde
#3 group-3293038-3.patch180.8 KBkristiaanvandeneynde
#2 group-3293038-2.patch143.31 KBkristiaanvandeneynde

Comments

kristiaanvandeneynde created an issue. See original summary.

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
commented
Status: Active » Needs review
StatusFileSize
new group-3293038-2.patch143.31 KB

Still needs a lot more work, but it's a start.

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
commented
StatusFileSize
new group-3293038-3.patch180.8 KB

A lot more renames in here. Would be great if we could rename the entity types for GroupContent(Type)

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
commented
StatusFileSize
new group-3293038-4.patch188.59 KB

Think I got most of it, too bad we're still stuck with GroupContent* class names and group_content* machine names

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.