Merge Request API about gitbeaker HOT 7 CLOSED

Missed that one, sorry about that.

from gitbeaker.

Just merged into 2.2.0 :)

from gitbeaker.

So by importing mergerequest model and exposing it to the api I can use it.

Only issue was that there is a first parameter https://github.com/jdalrymple/node-gitlab-api/blob/master/src/Models/MergeRequests.js#L4 projectId which doesn't get used. Is there a reason for it, as all the other endpoints I used don't have it.

from gitbeaker.

Seems like exposing that makes sense, otherwise not sure how you'd use it. And I'd agree that the first parameter seems unnecessary. There are some more options for the MR API (like this one https://docs.gitlab.com/ee/api/merge_requests.html#list-project-merge-requests) that need it but the all() call doesn't have an option for it.

from gitbeaker.

@arsdehnel that one is already in this model https://github.com/fewieden/node-gitlab-api/blob/master/src/Models/ProjectMergeRequests.js#L27

from gitbeaker.

Do you have an eta when this will be published to npm, as i have some building issues in my automatic pipelines with my fork? Just need to know if I have to workaround it or it will be available in couple of days.

Thanks in advance

from gitbeaker.

Yup! Will be publishing today, just need to test that parse change before I publish

from gitbeaker.