The update function is really nice - no question.
But (sorry, that's me ..) I would like to see what have changed and why there is a update.
Maybe the changelog could be displayed?
Best would be th show the difference between the installed and the new version.
Reason (beside my personal preference to know what is going on and why): if it is a security update, it should be done immidiately.
If not, it could be done later.
Basically, the store owner should have the possibility to know what is updates and why BEFORE he is doing it.
What do you guys think?
But (sorry, that's me ..) I would like to see what have changed and why there is a update.
Maybe the changelog could be displayed?
Best would be th show the difference between the installed and the new version.
Reason (beside my personal preference to know what is going on and why): if it is a security update, it should be done immidiately.
If not, it could be done later.
Basically, the store owner should have the possibility to know what is updates and why BEFORE he is doing it.
What do you guys think?
Share this post:
Responses (2)
-
Accepted Answer
Agree, we use that for our Joomla components by displaying a remote article.
Will see if we can get the raw format of releases description from GitHub https://github.com/arastta/arastta/releases/tag/1.0.3 -
Accepted Answer
Yes we can
https://developer.github.com/v3/repos/releases/#get-a-single-release
"body": "Description of the release",
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »