Help shape the future of CurseForge!

Show changelog when updating

When updating an addon it is tedious to check the changelog.

Currently, what is needed to see it:

1. Click the addon

2. Wait until the addon's page loads

3. Click Changelog

4. After reading the changelog you need to press "Back" to return

This becomes even worse when you need to update several addons.

I suggest a UI component, that will contain a changelog. Each addon in the list will have its own component. This can be implemented as a button "Changelog" - the closable window opens when pressing it. Or it can be a closable popup/modal when hovering for some time over the version field. The window will contain a scrollable text with the sought changelog.

You can go further and provide a diff of a changelog. E.g., if a person has version 1.1 and the addon is now version 1.3, the component shows changes for versions 1.2 and 1.3, but does not show for version 1.0. This will also remove the need of remembering your original version when checking a changelog.

Additionally, from my own behavior I know that I often just press the button "Update all". But after pressing it there is a downtime and I have a thought in my mind "wish I could know what I am getting". Therefore, as another QOL improvement there, it would be nice to have a component which shows a collected changelog of all updating/recently updated addons when pressing "Update all". Again, it can be accessed through a button or closable popup shown automatically after pressing.

This is suggested looking on WoW addons. But it should be possible to do this for other games as well if they have changelogs as well.

Thank you.

  • dartweder7
  • Feb 20 2021
  • Future consideration
  • Attach files
  • dartweder7 commented
    21 Feb 11:15am

    Thank you! I'm here if anything.

    The only complication from the development perspective I can think of: there seems to be no strict format for an addon's versions. So it is possible that there will be versions like 1.2-alpha and 1.2-beta or something worse. It would be better to somehow check all possible kinds of version string first. And also handle the case when a version was not recognized.

  • Admin
    Team Overwolf commented
    21 Feb 09:13am

    That's a sweet suggestion! thanks, logging in :)