Error with current user route and its Pydantic model

[JimScope]

Describe the bug

In beanie the id field returns null when the Current User path is used. Like nested documents.

To Reproduce

Steps to reproduce the behavior:

• Clone the repo
  svn export https://github.com/fastapi-users/fastapi-users/trunk/examples/beanie
• Configure the database, in this case I use MongoDB Atlas
• Create a user using FastAPI
• Obtain user data with the router: Current User

Expected behavior

{"id":"d23d8h293dj3298","email":"user@example.com","is_active":true,"is_superuser":false,"is_verified":false,"messages":[{"foo": "bar"}]}

but the id field and other custom field return null

{"id":null,"email":"user@example.com","is_active":true,"is_superuser":false,"is_verified":false,"messages":null}

Configuration

• Python version : 3.10.4
• FastAPI version : 0.78.0
• FastAPI Users version : 10.0.4

FastAPI Users configuration

None.

Additional context

None.

[frankie567]

Hi @JimScope!

Could you show us how you configured the Beanie model and the Pydantic schemas?

[JimScope]

Thanks to reply @frankie567 . I have not changed anything from the example that is in the repo. Attached the MongoDB Atlas database document
{"_id":{"$oid":"628bb94e4c07ea5954e9a693"},"email":"user@example.com","hashed_password":"$2b$12$qX64ExUF0r.wN4Pgc2qpRO3e6a/NQZST84lq1qDOiiw2cwZVvq72K","is_active":true,"is_superuser":false,"is_verified":false}

[JimScope]

As you can see the id value exists in the document, however it is not retrieved when the /me path is used. Returning a null value

[frankie567]

After checking, the id is indeed null. I'll investigate, thank you for reporting!

[frankie567]

Should be fixed in v10.0.5 🎉