The return of null for any field in the response for this api call is undocumented and should not be allowed.
I could see a few errors on production related to the transform function using statistics.count while statistics is null, resulting in TypeError due to the call of a field of undefinied.
This fix both uses upstream api as intended and avoids future issues for calling fields of an undefined value.
* allow serviceData to override cacheSeconds with a longer value
* prevent [endpoint] json cacheSeconds property exceeding service default
* allow ShieldsRuntimeError to specify a cacheSeconds property
By default error responses use the cacheLength of
the service class throwing the error.
This allows error to tell the handling layer the maxAge
that should be set on the error badge response.
* add customExceptions param
This
1. allows us to specify custom properties to pass to the exception
constructor if we throw any of the standard got errors
e.g: `ETIMEDOUT`, `ECONNRESET`, etc
2. uses a custom `cacheSeconds` property (if set on the exception)
to set the response maxAge
* customExceptions --> systemErrors
* errorMessages --> httpErrors
* feat: add gitlab issues service
* fixes based on review
* fixes based on review
Co-authored-by: repo-ranger[bot] <39074581+repo-ranger[bot]@users.noreply.github.com>