No efficient way to track which Individuals change status as favourites
Submitted by Travis Reitter
Assigned to fol..@..e.bugs
Link to original bug (#697082)
Description
If a client wants to keep a working set of the Individuals which are favourites, the only option is to connect to notify::is-favourite on all Individuals. This obviously doesn't scale very well.
We should add a property to IndividualAggregator like "Set<Individual>
favourites" which will be valid (exhaustive) after the aggregator is quiescent. Clients that care about favourites generally want to do something with the set of favourites, so this would handle that case well in addition to the signalling.
We could potentially add a special signal for the equivalent of individuals-changed, though it may be overkill as the set of favourites should be small enough that iterating through the set to handle just the changes should be fine. But if we care about the worst case, we should probably add favourites-changed.
Version: git master