Problem/Motivation
#3096078: Display core compatibility ranges for available module updates was committed before a usability review.
It adds a lot of (mostly duplicate) text to the available updates report:
We should try to improve the UX of this info because it's:
a) Important.
b) Likely to grow larger and more complex over time.
Proposed resolution
- Make "not compatible" a details that replaces download link
- Add a details under download link for compatible releases
Remaining tasks
UX review.Brainstorm solutions.Implement them.Initial prototype in #26- Improve implementation,
remove @todo's, etc. - Update / fix failing tests.
- Adding new tests?
- Fix styling.
- Reviews:
- UX
- Code / implementation
- RTBC.
- Commit.
- Followup for the 9.0 Usability review of the major version update
- Followup to do a UX review of the update status report once other semver work is implemented in core and on Drupal.org as a part of #3110198: [META] Beta targets following Drupal 9.0.0-beta1
User interface changes
Initial, ugly prototype from #26 (screenshots from Seven):
Compatible
Initial
Open
Incompatible
Initial
Open
API changes
Probably nothing public. Some changes to @internal API of some update classes (esp ProjectCoreCompatibility).
Data model changes
N/A
Release notes snippet
TBD. Probably not needed since this is just cleaning up another feature that hasn't yet been released.