Closed annathecrow closed 10 years ago
The restful-api
would definitely replace api
. I kept it because it was too bloody complicated to switch branches all the time when I was setting everything up, and then I didn't thought about nuking it.
Should I clean this up and push the edits, or should I wait before you finish what you're doing on url-params
? We'd be working at the same files, that could get hairy very fast.
So, this belongs to #11. I didn't want to change the original api Blueprint, so I made a new one. I dunno. It wouldn't be hard to work in into what we already have, I guess. I guess I'd have to do more digging in the functions to get most of it. The parser is nice, and I like the routing, too. It has a lot of other functions I didn't find use for, but I think I wasn't really looking that hard. If you aren't especially attached to the idea of using as little packages as possible, I'd go for it.