ListMember to no longer use Namer

This commit broke ListMember to remove the Namer interface. This is because the whole interface should act as a static container with information to be updated.
diamondburned · Mar 25, 2021 · 0cb14b9 · 0cb14b9
1 parent f24feb2
commit 0cb14b9
Show file tree

Hide file tree

Showing 3 changed files with 24 additions and 11 deletions.
diff --git a/cchat.go b/cchat.go
diff --git a/repository/gob/repository.gob b/repository/gob/repository.gob
diff --git a/repository/main.go b/repository/main.go
@@ -1833,18 +1833,28 @@ var Main = Packages{
 			},
 		}, {
 			Comment: Comment{`
-				ListMember represents a single member in the member list. This
-				is a base interface that may implement more interfaces, such as
-				Iconer for the user's avatar.
+				ListMember represents a single member in the member list. Note
+				that this interface should be treated as a static container:
+				updating a member will involve a completely new ListMember
+				instance with the same ID.
 
 				Note that the frontend may give everyone an avatar regardless,
 				or it may not show any avatars at all.
 			`},
 			Name: "ListMember",
 			Embeds: []EmbeddedInterface{
-				{InterfaceName: "User"},
+				{InterfaceName: "Identifier"},
 			},
 			Methods: []Method{
+				GetterMethod{
+					method: method{
+						Name: "Name",
+						Comment: Comment{`
+							Name returns the username or the nickname of the
+							member, whichever the backend should prefer.
+						`},
+					},
+				},
 				GetterMethod{
 					method: method{
 						Comment: Comment{`