User IDs are strings since we have moved our authentication system to auth0. This was raising a validation exception when loading the data returned by the API. This bug wasn't caught until now because:
we were using dataclasses until very recently which were not applying validation when unserializing data
after switching to pydantic, this is not caught in our e2e tests because all the users used for the e2e tests are users that existed before the migration to auth0 and hence their IDs were reused when we moved to auth0. Hence they still can be parsed as integers.
User IDs are strings since we have moved our authentication system to auth0. This was raising a validation exception when loading the data returned by the API. This bug wasn't caught until now because: