Implement the ability to use shorthand for semantic versions
What does this MR do and why?
Implement the ability to use shorthand for semantic versions - @1 or @1.2
This will be used for includeing a component and it supports eitherone or two digit shorthand. For both cases it will return the latest version for the closest match.
Changelog: added
Screenshots or screen recordings
With the following releases, created in this order: 3.2.0, 3.1.2, 5.0.1
5.0.1
we can use 5 :
or 5.0 to narrow it down:
For 3.1.2 and 3.3.0
Since 3 will bring us the latest, this means 3.3.0, even though 3.1.2 was released after, since we're returning the latest semantic version.
If we narrow it down to 3.1 it will bring us the patch 3.1.2
And then 3.1 it will bring us the patch 3.1.1
How to set up and validate locally
For this to be tested, you must have a project set up as a catalog resource and a few versions associated with it. From there you can try including the component in the editor and see it work like the screenshots above.