Skip to content

Release order is implicitly determined by ordering of objects in index.json #512

Description

@ekorchmar

Describe the bug
Latest release on multiple screens may be determined incorrectly (for example, if gathering Achilles statistics for releases was done out of chronological order).

To Reproduce

  1. Run DQD and Achilles for newer release.
  2. Run DQD and Achilles for older release.

Expected behavior
Newer release as determined by any of the date fields is shown as latest release on the main screen.

Actual behavior
The older release is shown as the latest one.

Screenshots
NDA

Desktop (please complete the following information):
Microsoft Edge on Windows 10

Additional context
This (and other code) should look for information in date fields to determine the latest release, and explicitly sort by them, not trust a 0-indexed object to always be the latest release. Our team worked around the bug by manually editing the index.json file to rearrange the release objects in the array.

{{ slotProps.data.releases[0].release_name }}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions