Edit Question - KnowledgeHub

Title Body

I have started playing around with immutable value objects in Java while working on a game project, following the "public final fields" approach: public class Team { public final String name, flag; public Team(String name, String flag) { this.name = name; this.flag = flag; } } This works pretty well for me so far, but I need different sets of extra information about the team in different circumstances. For example, a team has a set color during a match. The question is, what is the best way to deal with these sets of extended information? I know this is a fairly general question, but I want to keep using immutable objects and that might influence the solution. Here are the options I have come up with. Most of them are probably "good enough", but I'd like to learn some arguments for and against them for future reference. Option 1: Everything in one class public class Team { public final String name, flag, colorName; public final int colorRgb; public Team(String name, String flag, String colorName, int colorRgb) { this.name = name; this.flag = flag; this.colorName = colorName; this.colorRgb = colorRgb; } } This takes only one class for all uses, but there is no type-based indication of what extra data is expected/provided. Option 2: Subclassing public class TeamWithColor extends Team { public final String colorName; public final int colorRgb; public Team(String name, String flag, String colorName, int colorRgb) { super(name, flag); this.colorName = colorName; this.colorRgb = colorRgb; } } This might make a content-based equals() implementation impossible. Option 3: Composition public class TeamWithColor { public final Team team; public final S

Tags (comma-separated) Cancel