-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Available version check #282
Labels
Comments
Good idea! Though I think it would be easier to implement a method in SiteApi instead of a http request. |
Forgot about that but yes you're right. |
Sounds like a good idea, but not on "path" please :) (used for every compilation) |
Yeah, as discussed and implemented in #283, it's done only for |
I know, just completely forgot about this issue even though I opened it :) Thanks for closing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm pretty sure (from experience) that most people don't know about self-update and end up using the bundled haxelib until the next haxe version.
We should really indicate to the user when a new version of haxelib is available.
The test would be quick, getting something like
http://lib.haxe.org/latestVersion/haxelib
which would contain only the semver (so very light).It would be at least on the commands that already connect to the internet, and we should probably cache the result too.
That way we can really send bug fixes and improvements.
I think it's important to ship that feature with haxe 3.3.
The text was updated successfully, but these errors were encountered: