response.data is {} when it should be null

[SavioR0]

Below is the link to the minimum code to reproduce the issue:

https://github.com/SavioR0/NoneBug

When the email received by the backend is an empty string, the code should return None.

Backend

@app.get(
    "/api/v1/users/email/{user_email}",
)
def read_user_by_email(email: str) -> UserPublic | None:
    """
    Get a specific user by email.
    """
    if email != "":
        print("Not none")
        return UserPublic(name="User", age=10)
    print("None")
    return None

Output:

None

However, the frontend receives {} even when the string None is printed on the backend.

Frontend

async function remoteCall(){
    const response = await UsersService.readUserByEmail({
      query: {
        email: "",
      },
    })
    const data = response.data
    console.log(typeof data)
    console.log(data)
}

Output:

object
{}

[mrlubos]

Hi @SavioR0! Yep, aware this is an issue, I was waiting until someone brings it up. The reason is the object is used to verify if the response was successful or not to narrow down the types. We'll need to modify this to include an alternative approach so we can preserve the original response data. Is this a blocker for you or an inconvenience? Thank you for reporting!

[SavioR0]

It's an inconvenience that I bypassed this way

const data = response.data
if (data && Object.keys(data).length > 0) {
 ...
}