Closed leojpod closed 6 years ago
@DennisSchwartz in this state the stats are loaded from the dataset or request model and are not pulled from the favourite service directly by the Front-end. However, the always increasing favourite count reappeared which I guess is caused by the deleting event not being picked up by the domain hosting the dataset/requests, what do you reckon?
Note: I've check the data returned by the calls to these info on prod and they do return the erroneous number of favourites
This should not be merged until the problem mentioned above is resolved.
@leojpod What are we doing with this now?
merge it? 😶
@DennisSchwartz it should solve the metrics issue while preserving the favcounts behaviour :)
Go for it then :)
We don't need the FavCount mixin anymore since the dataset now receives the correct favourite count. This will fix DIS-259 and DIS-266 was caused by a stupid name conflict while trying to attempt to fix the favourite count.