[Feature] Limit number of updates shown for users.
What is the problem? When showing changes logs in the website, there is a possibility that a user might login after a really long time when he will he fed with too many changes making it difficult for the user to go through all the changes.
Your solution
We can limit the number of logs shown to an appropriate count(n). Also, we can't just choose the last n updates as the user might miss some major updates that happened earlier. For this purpose, we can add a field called isMajorUpdate in change_log table, which will be set if we think it's a major update and users should definitely know about it.
So, the condition will be, fetch latest n number of updates along with major ones since he last visited the site. We could also improve to have the final logs match the count(n) by fetching less of minor updates.
Additional context If feasible, we could make carousal for such updates to have GIFs which explains the usage of that update.
Love this!