https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    yes, glad to see that it has benefits outside of haxelib as well
  • a
    haxelib would totally benefit from an ecs app design 😈
  • b
    arguably the part im going to find most useful: git history (ready to checkout, so i can go back and forth) 🙂
  • b
    (apart from the "create release" ofc - thats the thing im after "right now")
  • b
    @big-angle-82801 - before i reinvent the wheel, what options are available to me to zip and submit haxelib releases? (sorry for all the Q's!)
  • b
    is there a way also to kinda "test" a .zip release, like a "fake submit" or something to know if its valid or not? (im assuming there isnt)
  • b
    https://github.com/HaxeFoundation/haxelib/blob/development/src/haxelib/client/Main.hx#L367-L396 I think this is what we talked about before, this is what was meant to change once the password upgrades happen (which never did... 😅)
  • b
    it's in the Connection class
  • b
    neko only?
  • b
    no I think that block there is for some other thing andy was doing on js, not really sure
  • b
    but it should work anywhere hopefully
  • b
    Connection.submitLibrary
    basically?
  • b
    yes, and you pass a function which receives an array of contributors and prompts the user to provide login details
  • b
    thats neat and tidy 👌
  • b
    what about creating the zip? I guess i need to do that myself?
  • b
    also, is there any facility to kinda "test" whether a .zip is valid? Either locally (via the haxelib lib) or remotely (via some call that will do all the submit bits, but not actually update the db)
  • b
    it detects whether it is a zip or directory
  • b
    if it's a directory it zips itself
  • b
    right, but ill want rules to not zip "everything"... so i guess ill need to create the zip myself then?
  • b
    well for that you could just run submitLibrary and throw when prompted for the login, the checks happen before that. Apart from that it the code isn't very well structured for allowing that, definitely something to look into though
  • b
    Yes, in that case you'd just have to zip it yourself
  • b
    cool - that sounds good - and so i also assume there is no facility in haxelib itself to upload and test a .zip (or is the code that validates it on the client the same as the code that validates it on the sever?)
  • b
    It should be the same between the server and client in terms of validity of haxelib.json and stuff like that, but not 100% sure
  • b
    OK, cool - better than nothing then... thanks for the info
  • b
    i think the haxelib docs also say to run 
    haxelib submit .
    and just exit when prompted for login, which prevents the actual upload to the server but still validates the data
  • b
    cool - i figured there was something "extra" going on server side, but if there isnt, thats great, and even if there is, basic validity check is pretty good (better than the old version i wrote which did nothing of the kind)
  • b
    man, the callbacks for the submitlib are gonna be great... they are gonna fit in perfectly i think... 🥳
  • b
    starting to feel very "real" 🙂
  • p
    This look awesome. Way more than I need for that "1 line of code That I commit daily" but really cool
  • s
    haxeui raylib?
1...152215231524...1687Latest