> not be based on anything technical, but on how an API is used in practice Since it's an api, the "in practice" is some other piece of code, so I would still

> not be based on anything technical, but on how an API is used in practice Since it's an api, the "in practice" is some other piece of code, so I would still call it a technical issue.