Skip to content

Order of canonical-data keys #1705

Closed
@SaschaMann

Description

@SaschaMann

From @ee7 in #1703 (review)

But two questions:

  1. Do we have an official ordering that the keys are supposed to be in?

  2. If so, should we enforce the key order during CI? Maybe it helps with readability when adding tests. The ordering seemed pretty consistent before, but there will be nearly double the number of keys now.

I notice that the reimplements in this PR is after uuid, but when I made my recent PRs I instead ordered the keys as I saw them in #1674, that is:

  {
    "uuid": "82d32c2e-07b5-42d9-9b1c-19af72bae860",
    "description": "two times one is two",
    "comments": ["Expected value is changed to 2"],
    "reimplements": "e46c542b-31fc-4506-bcae-6b62b3268537",
    "property": "twice",
    "input": {
      "number": 1
    },
    "expected": 2
  }

Tasks:

  • Decide if there should be an order
  • Decide on an order
  • Convert all data to the right order
  • Add a CI check for it

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions