Skip to content

Fix issue where SQL calls don't use the default limit properly

  • Fix issue where SQL calls don't use the default limit properly

While previously the static config lookup worked for retrieving the limits, this appears to have broken at some point leading to this regression. The API will now use the default limit set in configs when no explicit value is set.

Resolves #75 (closed)

Merge request reports