Closed aduros closed 10 years ago
Adding "version : 0" to the return object that throws the first error fixes this, but who knows how permanent that solution is. I'm guessing the version property became obsolete, but the code that checks for it elsewhere did not.
With latest format and hxsl, everything should work correctly now.
Do you think you could still specify the required format version in haxelib.json? hxsl simply doesn't work with anything before 3.1.0, so it should specify that.
I think that would also fix flambe/hxsl update issues not pulling down the new format version: https://groups.google.com/forum/#!msg/flambe/ErLdE9lRVdg/TFBp5wf4cqoJ
Well, installing the latest hxsl should install the latest format as well.
It looks like it is installed, but the .current
file isn't updating to point at the new version. Changing hxsl to specify the version seems to fix it in that case.
This affects users upgrading from flambe 4.0.0 to 4.1.0 (aduros/flambe#293).
Uhm, that's not normal behavior. Does it affects only people that had installed the hxsl that explicitely defined the format version ? Usually haxelib would updrade all the dependencies
This breaks new Flambe installs and anything else that depends on hxsl. :(
Do you think you could explicitly specify the dependency version in haxelib.json to prevent this from happening again in the future?