Skip to content

Conversation

@ehsankhf
Copy link

@ehsankhf ehsankhf commented Jul 5, 2017

For the case of calling the

Job.get(undefined,()=>{})

It will raise an exception as the id's error is sent back by the non-determined third argument which is undefined.

The fix provides the correct order of argument validation inside the considered function.

… to {jobType} arguments, in Job.get method
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant