David Lumm

Ah that's great, thanks! I'll take a look at that and see what I can work out!

Hey all! I was wondering, is there any concept of "middleware" or hooks that I could attach to so I could run something on every request? At the moment I've got a couple of things I've added into every route function, but I can anticipate that list getting longer. Rather than copy and paste the same lines into each and potentially miss something, it would be great if I could run it before the route specific code runs. Is that possible @Sebi?

Thanks for your quick work on this @Sebi. That seems to have fixed it for us!

Hi all. I think we have a serious problem. I'm just trying to prepare an API that I've developed for release and I can't create new applications. Something to do with the default application flag, I think: https://github.com/Sebiworld/AppApi/issues/16 @Sebi is there anything I can do to help get this fixed quickly?

Great work @sebi! Am I reasonably safe to upgrade to the 1.1.0 version, it won't break anything?

Hi @Sebi I'm pretty new to ProcessWire and I've started using your module to add an API. I'm really appreciating all the work from you and @thomasaull as it's making my life much easier! I've spotted a couple of issues around HTTP statuses, one of them I've managed to do a PR for, it was pretty straightforward. The other issue is potentially a bit more complicated, or at least requires a bit of careful thought. Currently you can't set the response code, it's just hard-coded to 200, but I'd like to send a 201 on create. I can think of at least two ways of doing it, one is quick but messy: return the status as part of the handler response; the other is probably neater but needs choices to be made: add a function (but where? AppApiHelper?) that stores the status and then retrieve it in the router. Any thoughts?