Fix #70

[mdsb100]

No description provided.

[dave-irvine]

Ok I need @moul to weigh in on this, but if we are passing in a params argument, shouldn't projectId and hookId be contained within params now?

[mdsb100]

add: (projectId, params, fn = null) =>
    if 'string' is typeof params
      params =
        url: params
    @debug "Projects::addHook()"
    @post "projects/#{Utils.parseProjectId projectId}/hooks", params, (data) => fn data if fn

I just imitate the function "add" in ProjectHooks.coffee.
I read api/projects, I prefer this:

update: (projectId, hookId, url, params = {}, fn = null) =>
    @debug "Projects::saveHook()"
    params.url = url
    @put "projects/#{Utils.parseProjectId projectId}/hooks/#{parseInt hookId}", params, (data) => fn data if fn

[moul]

It sounds like #33
I think too that a common interface everywhere would be the best solution, but it will also break the whole compatibility and need a new major release

since we don't have named arguments in javascript, I think the object params is the best solution to handle optional parameters and to help people call functions without thinking about parameters order

We need more thought, but I personally like the idea of standardised parameters everywhere, it will also be easier to use a marshaller to validate arguments