-
Notifications
You must be signed in to change notification settings - Fork 28
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
Refactor the app to allow choosing between next minor and major update #391
Conversation
Codecov Report
@@ Coverage Diff @@
## master #391 +/- ##
=============================================
+ Coverage 41.03% 52.84% +11.81%
- Complexity 229 278 +49
=============================================
Files 15 17 +2
Lines 775 931 +156
=============================================
+ Hits 318 492 +174
+ Misses 457 439 -18
Continue to review full report at Codecov.
|
we'll also need the |
Build is failing due to a version bump in core:
|
set max-version to 11.0.0.0 for now |
@felixheidecke any thoughts ? We could split the "Update info" column into three:
Might then need two buttons, or make the update target clickable to select which one to update to. Or a dropdown to select the version ? |
and now I realize that whatever the UX will be it will have an impact on the info that the controller endpoints must return... |
@PVince81 it has even more impact than you can imagine ;)
I managed to pass both versions to frontend and display them Imo for two candidates the right side should mutate into the HTML select element |
@VicDeo go for it :-D |
e6931d6
to
473c395
Compare
@PVince81 another questionable thing is |
@VicDeo if Is there a possibility to specify a version number to install like with Linux package managers ? |
@PVince81 >Is there a possibility to specify a version number to install like with Linux package managers ? no, it installs the most recent, or updates to the most recent if the app is already installed. |
075fc2e
to
a5663c6
Compare
@PVince81 it's hard to say as I still suck in the frontend part :( |
@VicDeo you can get some advice from @felixheidecke in the chat |
@PVince81 @felixheidecke I updated the PR description with a new look for I appreciate the advice on the app details tab given that both releases could have missing dependencies section here... |
What would be correct to use from the point of UI here, radiobutton? |
I am missing the context here. Is it in regard to the screenshot above? What is to be chosen? |
@felixheidecke the context is providing two versions for update: minor and major, |
The dropdowns in the screenshot in the very first post look good. Don't they suffice? |
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.
Looks good in general. See a few comments.
@PVince81 answered everywhere |
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.
👍
In this scenario: Do we feel OK with the text shown? Is it clear enough for an admin?
(cc @pmaier1 ) |
When exactly is this message shown? Only when there's a requirement for |
let's clarify UX and messages in #416 |
Summary
Core upgrade (this part depends on owncloud/core#32491 that is still WIP)
CLI
market:upgrade
still DOES upgrade 1.0 to 1.1market:upgrade
does NOT upgrade 1.0 to 2.0market:upgrade --major
DOES upgrade 1.0 to 2.0market:install
does NOT upgrade 1.0 to 2.0 if the app is already installedmarket:install
still DOES upgrade 1.0 to 1.1 if the app is already installedMarket app Web UI
Market app cron job
Screenshots
Updates tab
App Page
TODO
--major
option to CLImarket:upgrade
commandmarket:install
command(Depends on Pass an additional parameter on the core update core#32491)
0.3.5 to 0.3.5
0.3.5 to 1.3.5 (no
--major
)0.3.5 to 1.3.5 (with
--major
)after the merge