I’m calling it a night. Feeling somewhat defeated by these leaf templates. But I’ll figure it out. Eventually I’ll finish one of these side projects.
@jsorge Did you find the issues yet? I’m wrapping up a Vapor 3 project right now and encountered all sorts of Leaf issues along the way. I’m happy to take a look if you'd like!
@brandon Oh nice! I might take you up on that. I haven't found the problems yet, but was getting an error about the number of parameters sent in vs expected (0/1) but it didn’t say what element it was for. I'll probably take another run at today.
@jsorge Sounds good - just let me know if you'd like me to take a look. That particular issue doesn't ring a bell, but I bet we can figure something out.
@jsorge I tried updating to Vapor 3 a couple of sites (one complex and my blog which is pretty simple) and I've found I would need to basically … rewrite everything 😞 How's it going for you?
@rolandleth The site that I'm upgrading is super trivial. Mostly static pages with a content form. The upgrade has been pretty smooth but the Leaf changes threw me for a loop (pro tip: You have to escape } characters inside of #set(){} blocks).
@jsorge Ah, okay. I have quite a few controllers, custom leaf tags and DB communication — these have changed entirely 🤪 Thanks for the leaf tip!
@rolandleth As I'm playing with it more I think I'll probably write something more complicated in the nearer future (hopefully I won't need a DB though). I really like what I'm seeing from it. Hopefully Vapor will be stable going forward; each version being a massive breaking change is tough to swallow.
@jsorge Aye, it really is, especially 2–>3. I’m really hoping 3–>4 won’t be the same, or I’m gonna totally regret not sticking with Node.js. If it weren’t for the novelty and learning benefits of it, I would’ve regreted already.