Skip to content

Minor improvments on Alizer's min/max version CLI arguments #1182

Closed
devfile/alizer
#11
@thepetk

Description

@thepetk

Which area/kind this issue is related to?

/area alizer

Issue Description

As discussed here #1170 (comment) after the addition of min-version and max-version a minor improvement could be made regarding the naming of the argument and the response of alizer.

  • Right now we use min-version and max-version and we may have some confusion between devfile version and schemaversion fields. So we could rename the args to - min-schema-version and max-schema-version

  • Inside the response of alizer we could include the version of a matched devfile:

$ ./alizer devfile --min-schema-version 2.2.0 --max-schema-version 2.2.0 ~/github/thepetk/go-ps-script

[
	{
		"Name": "go",
		"Language": "Go",
		"ProjectType": "Go",
		"Tags": [
			"Go"
		],
		"Versions": [
			{
				"SchemaVersion": "2.2.0",
				"Version": "1.1.1",
				"Default": false
			},
			{
				"SchemaVersion": "2.2.0",
				"Version": "1.1.0",
				"Default": false
			}
		]
	}
]

Metadata

Metadata

Assignees

Labels

area/alizerEnhancement or issue related to the alizer repo

Type

No type

Projects

Status

Done ✅

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions