Closed ghost closed 9 years ago
Building failing :(
Also at this point, not much need for isPath
, isForm
, etc... The purpose of these was when multiple parameter.in
types were being lumped together into a single type. At this point they are entirely distinct.
My bad, forgot to run tests locally first. I've tweaked the test to reflect the value coercion on req.query that's now happening in expressroutes.
I'm not quite following re. the isForm, isPath piece - were you thinking of just swapping in another switch to pass through the coerced values from the validator there?
See above for what I'd suggest re dropping isPath etc. Basically moves to an accessor pattern, drops the switch logic into an object lookup and breaks up the longer function into smaller fn calls.
LMK if it seems reasonable, also happy to tweak to fit another preferred pattern.
hmm, will look at the travis errors. tests seem happy locally
couple of lint issues, now fixed
I like this, but can you remove lodash
usage? It was an unused dependency left over that needed to be removed.
Also, sorry this is taking so long! I appreciate the patience.
no problem. I've pushed a version w/out lodash now - I left the dep in the package.json file for now though, lmk if you'd like me to remove.
If this seems good I'll squash up the commits and get it ready for merge.
On the face of it, seems ok (with exception of code style comment). Will get another from team to review as well!
LGTM. Code consistency is important but I would argue for functions assigned to variables.. Maybe merge this and we can argue about that later.. :+1:
…values in the query string.
Closes krakenjs/swaggerize-express/issues/64