-
-
Notifications
You must be signed in to change notification settings - Fork 720
Added ability to see changelog from the add-on store and Updatable add-ons dialog #18816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I'm also working locally modifying files of the addon-datastore-validation repo. Also this would need to be added to the documentation (metadata) of the addon-datastore repo. I'll work on this if the direction of this PR is right. |
I think the most useful place to read the change log would be from the add-on update dialog. I think from the add-on store lists, it should be a button like |
@seanbudd, I'm trying to convert markdown to HTML with the markdown.markdown function, but the manifest model doesn't support the strip method, and the conversion is not performed. I have displayed the browseable message with a button from the context menu, but seems that markdown conversion is difficult to achieve with the manifest. |
@nvdaes wouldn't calling |
Sean wrote:
Thanks! It works now. |
…ndicate that this will open a dialog
Now we can see the changelog from the installed add-ons list using Actions or the context menu, and when updatable add-ons are found, from the Update add-ons dialog.
|
Descriptions were presented instead of changelogs in the updatable add-ons dialog, since I used the description key for testing. @seanbudd , when I try to use the changelog key, errors are raised since changelog is not available from data. Perhaps would be better to add changelog to addon-datastore-validation before finishing this PR? |
I think that we can finish this PR before working in addon-datastore-validation. Now I don't get errors. |
Now we use the virtual list available in the store dialog. Unfortunately, for now it's difficult to test this since I get the following error when trying to install an add-on. I think that this is not related to this PR: ERROR - unhandled exception (21:13:46.401) - MainThread (6012): |
nvda.log |
@nvdaes - are you still encountering this issue? |
@seanbudd , in fact I find this issue and also in a different PR which I opened to show spelling errors in braille. Please let me know if I should remove and clone NVDA from scratch or something. |
Have you merged in the latest nvaccess/master? Is the issue occurring with both alpha and the installer built from the PR by GitHub action? Can you share the log with us? |
I've merged the master branch and I get this error running from source. I'll test the snapshot and alpha and will share the log, and if I still get the error. |
Thanks @SaschaCowley Most issues are fixed by PR #18952 There is still an issue, but I don't know if this should be fixed by this PR. I find it also in NVDA 2025.3rc1 This happens when the option to update add-ons automatically is checked. |
I think that this is ready for review, though some system tests failed. |
from .actions import _MonoActionsContextMenu | ||
from .addonList import AddonVirtualList | ||
from gui.addonStoreGui.viewModels.store import AddonStoreVM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can any of these imports be moved to top of file?
closeButton = bHelper.addButton(self, wx.ID_CLOSE, label=pgettext("addonStore", "&Close")) | ||
closeButton.Bind(wx.EVT_BUTTON, self.onCloseButton) | ||
|
||
def _createAddonsPanel(self, sHelper: BoxSizerHelper): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are several issues with this new design:
- the buttons to open the store, update all and close are not visible
- the table is clipped and doesn't contain the full information. Instead the table should fit the dialog, and the dialog should be wider.
Co-authored-by: Sean Budd <[email protected]>
Link to issue number:
Fixes #14041
Summary of the issue:
Users may want to see changes included in the current version of add-ons, especially to decide if they want to update them, and to get an idea of new features, bug fixes and so on.
Description of user facing changes:
List of changes will be shown in browse mode. If changes are writen in markdown, they will be rendered in formatted HTML. The title of that message will show the add-on version name, and buttons will be available to copy the info and close the browseable message.
Description of developer facing changes:
Add-on models have a new changelog property.
Description of development approach:
Testing strategy:
source/addonStore/models/addon.py
, in the_createStoreCollectionFromJson
function, add the following code just for testing:Check that changelog can be shown just for this add-on.
Also, changelog in markdown has been created in the manifest and in the store collection, to check that markdown is properly rendered in HTML in the store and in the Updatable add-ons dialog.
Tests have been done with the resourceMonitor add-on to check that the context menu can be used from the Updatable add-ons dialog.
Known issues with pull request:
Sometimes, NVDA says thw word "panel" when the changelog is opened.
Code Review Checklist: