Skip to content

LTF versioning #301

Description

@JonJagger

The display name for an LTF now includes version numbers. eg
Ruby 3.0, TestUnit 4.5

This could mean you pick that, go to clock [create], and just at that moment a languages-start-points deployment concludes, and that display-name no longer exists, eg it is now Ruby 3.0, TestUnit 4.6

Ideally we avoid this.
One option here is that you pick Ruby, TestUnit and that defaults to the latest 3.0, 4.5
but that if you wanted you could pick from all the known versions. Almost certainly overkill.

Feels like:

  1. I'd still like the version numbers to be visible
  2. I don't want them causing the above error.

Which suggests updating the manifest.json format?

{
  "display_name": "Java 4.5, JUnit 3.2",
  ...
}

might become

{
  "language": [ "Java", "4.5" ],
  "test_framework": [ "JUnit", "3.2" ],
  ...
}

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

    • Status
      Large

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions