Request info refactor about kakapo HOT 8 CLOSED

Since we want to align with Foundation as close as possible, may I suggest using queryParameters and components? @MP0w

from kakapo.

Fine for me

from kakapo.

related to #21

from kakapo.

I'll prefer instead something like this when declaring a handler like router.get('/users/:id') and performing a request like users/12?page=1&limit=10 with empty headers and body

{
  params: {id: "12"},
  query: {page: "1", limit: "10"},
  headers: {},
  body: {} 
}

Also, I don't like the HTTP prefix for any of the properties

from kakapo.

HTTP prefix is to align with the Foundation counterpart.
Your code is the same except the naming right?
Not sure if params is right because usually what you now called query is called params (that's why I was confused)

from kakapo.

Since /id/ is an URL component (NSURL call it that way) I was suggesting components, @joanromano ?

from kakapo.

Yes, my suggestion is all about naming, what i call query is usually called query or queryParams. I don't like components neither btw.

from kakapo.

I agree with @zzarcon in terms of naming, since Node.js names it in exactly this way

from kakapo.