Make clear why each XML update.module fixture is created the way it is

Created on 23 February 2020, over 4 years ago
Updated 15 April 2024, 6 months ago

Problem/Motivation

#3102724: Improve usability of core compatibility ranges on available updates report β†’ and other issues there has been confusion about why certain XML features were made they way they were.

We should make it clear.

Proposed resolution

  1. Add comments to each XML fixture in the update module that makes clear why it's data is the way it is
  2. Add comments to test methods to make clear which fixtures they use and why

They might be additions or better ideas for making this clear.

Remaining tasks

All the tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component
UpdateΒ  β†’

Last updated about 9 hours ago

  • Maintained by
  • πŸ‡ΊπŸ‡ΈUnited States @tedbow
  • πŸ‡ΊπŸ‡ΈUnited States @dww
Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024