Change Details

Currently, watchlist management is implemented in the User class. Factoring it out removes baggage from the User class, and helps with resolving the circular dependency between User and Title. Rough interface draft: * isWatched( Title, UserIdentity ); // was User::isWatched. Could use PageIdentity instead of Title, once we have this. * setWatch( Title, UserIdentity, bool ); // was User::addWatch and removeWatch. Could use PageIdentity instead of Title, once we have this.

Currently, watchlist management is implemented in the User class. Factoring it out removes baggage from the User class, and helps with resolving the circular dependency between User and Title. Rough interface draft: * isWatched( Title, UserIdentity ); // was User::isWatched. Could use PageIdentity instead of Title, once we have this. * setWatch( Title, UserIdentity, bool ); // was User::addWatch and removeWatch. Could use PageIdentity instead of Title, once we have this. User::isWatched, addWatch, and removeWatch should be deprecated. For the deprecation period, they can delegate to the new service via the global service locator.

Currently, watchlist management is implemented in the User class. Factoring it out removes baggage from the User class, and helps with resolving the circular dependency between User and Title. Rough interface draft: * isWatched( Title, UserIdentity ); // was User::isWatched. Could use PageIdentity instead of Title, once we have this. * setWatch( Title, UserIdentity, bool ); // was User::addWatch and removeWatch. Could use PageIdentity instead of Title, once we have this. User::isWatched, addWatch, and removeWatch should be deprecated. For the deprecation period, they can delegate to the new service via the global service locator.