Well, if I got you right I'd say that this metadata doesn't belong to the version. It sounds more like we're talking about a Release that consists of a Version and maybe some Metadata or even more specific objects.
In version object we can load some meta-data and when we up version by creating new object we must hand over this data for new object for close losing meta-data in new wersion.
It`s not important for solution on codewars. I`,m just trying talking with good programmer like u <3 about this.
Good idea with version class. But allways create new object with next version it`s a bad idea if we look in feature. Varsion can make some properties like 'path to artifacts', etc and best way will be increment integers in current object.
Well, if I got you right I'd say that this metadata doesn't belong to the version. It sounds more like we're talking about a
Releasethat consists of aVersionand maybe someMetadataor even more specific objects.In version object we can load some meta-data and when we up version by creating new object we must hand over this data for new object for close losing meta-data in new wersion.
It`s not important for solution on codewars. I`,m just trying talking with good programmer like u <3 about this.
Thanks for your comment. Can you elaborate on why you think creating a new object for each version is a bad idea?
Good idea with version class. But allways create new object with next version it`s a bad idea if we look in feature. Varsion can make some properties like 'path to artifacts', etc and best way will be increment integers in current object.
Oh, it`s very interesting solution=)