twitchdev / twitch-cli

The official Twitch CLI to make developing on Twitch easier.
Apache License 2.0
604 stars 71 forks source link

[Bug] Endpoint returns different response than twitch docs #292

Closed aaricdev closed 10 months ago

aaricdev commented 10 months ago

What is the problem?

When using the endpoint to receive all blocked users for a user /mock/users/blocks on a newly generated mock-api, the response looks like

{
    "data": null
}

According to the official docs, the response should be an empty array and after testing it, the response looks more like

{
    "data": [],
    "pagination": {}
}

This is just a minor thing, but in my case, I use the mock-api in automated tests to get more or less realistic results without touching the real Helix API. And because I expect an array there, my tests fail. Also, the pagination is missing, even though its empty.

Operating System

Ubuntu 22.04

Architecture Version (x86, x64, arm, etc)

x64

Steps to reproduce

  1. Start the mock-api twitch mock-api start
  2. Generate a user access token (https://github.com/twitchdev/twitch-cli/blob/main/docs/mock-api.md#auth-namespace)
  3. Send request to http://localhost:8080/mock/users/blocks?broadcaster_id={YOUR_MOCK_ID}

Relevant log output

No response