Commitment and Commitment Change Order End Points
When passing a valid project id to the Commitment end points if no records exist a 400 type error is thrown. An error should not be thrown for a valid job being passed to valid end point and we should not have to tweak our code to work around an error that is not an error. The API should either return an empty or null node if no records or gracefully return some json explaining that no records exist. Now if I passed in an invalid project_id or bad endpoint I would expect an error to be thrown but not when everything passed is valid.