Force app enable: check future compatibility
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: apps management
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
From: https://github.com/nextcloud/server/pull/14578#issuecomment-474252797
If there is an update available, we shouldn't show the force enable button? Cause the update might have compatibility with the new version. So actually there should only ever 2 buttons: 1) remove and 2) either enable, update or force enable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Start by locating the app-management UI and the logic that chooses action buttons when an update is available; done means showing Remove plus the appropriate enable, update, or force-enable action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100