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:
- I'd still like the version numbers to be visible
- 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" ],
...
}
The display name for an LTF now includes version numbers. eg
Ruby 3.0, TestUnit 4.5This 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.6Ideally we avoid this.
One option here is that you pick
Ruby, TestUnitand that defaults to the latest3.0, 4.5but that if you wanted you could pick from all the known versions. Almost certainly overkill.
Feels like:
Which suggests updating the manifest.json format?
might become