wbond / packagecontrol.io

The Package Control website
https://packagecontrol.io
Other
111 stars 46 forks source link

Multi-release setups with non-3000-based version requirements not rendered properly #93

Open FichteFoll opened 7 years ago

FichteFoll commented 7 years ago

The general functionality was added in #3, but I noticed this doesn't play well for the PackageDev package: https://packagecontrol.io/packages/PackageDev

Currently:

screen

The expected output should be as follows:

ST3|PRE: 3.0.0-alpha.4 ST3: 2.1.0 ST2/ST3: 2.1.0

The thing to note here is that I didn't specify 3000 as the release border but 3092. A such, there should probably be a tooltip for this on the second and third tag with the exact build requirement.


All tags on the repo:

0.5.0
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.0.8
2.0.0
2.1.0
3.0.0-alpha.1
3.0.0-alpha.2
3.0.0-alpha.3
3.0.0-alpha.4
st2-2.1.0

Package entry in the default channel:

        {
            "name": "PackageDev",
            "details": "https://github.com/SublimeText/PackageDev",
            "previous_names": ["AAAPackageDev"],
            "author": ["guillermooo", "FichteFoll"],
            "releases": [
                {
                    "sublime_text": "<3092",
                    "tags": "st2-"
                },
                {
                    "sublime_text": ">=3092",
                    "tags": true
                }
            ]
        },