[GH-ISSUE #98] Social entity won't let me add a username that contains periods and numbers (Ex. Facebook) #1037

Closed
opened 2026-05-03 01:54:58 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @NoName57 on GitHub (Jan 3, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/98

I'm trying to add an entity to my sketch for a Facebook account with the entity type of SocialAccount. It won't accept a valid social media account username from Facebook that contains periods and numbers. The Pydantic error in the log says:

Pydantic validation error: 1 validation error for SocialAccount

username.value

  Value error, Invalid username: [Example. FIRST.LAST.750]. Must be 3-80 characters and contain only letters, numbers, underscores, and hyphens. [type=value_error, input_value='[username again here]', input_type=str]

    For further information visit [https://errors.pydantic.dev/2.12/v/value_error⁠](https://errors.pydantic.dev/2.12/v/value_error)

This should be able to accept any valid form of username.

Originally created by @NoName57 on GitHub (Jan 3, 2026). Original GitHub issue: https://github.com/reconurge/flowsint/issues/98 I'm trying to add an entity to my sketch for a Facebook account with the entity type of SocialAccount. It won't accept a valid social media account username from Facebook that contains periods and numbers. The Pydantic error in the log says: ``` Pydantic validation error: 1 validation error for SocialAccount username.value Value error, Invalid username: [Example. FIRST.LAST.750]. Must be 3-80 characters and contain only letters, numbers, underscores, and hyphens. [type=value_error, input_value='[username again here]', input_type=str] For further information visit [https://errors.pydantic.dev/2.12/v/value_error⁠](https://errors.pydantic.dev/2.12/v/value_error) ``` This should be able to accept any valid form of username.
Author
Owner

@dextmorgn commented on GitHub (Jan 3, 2026):

Hey @NoName57,

Thanks for raising this issue.

Indeed, I considered usernames to be single string format. But the current validation is too strict and doesn't support your case, which I didn't consider.

I'll review the username validation and come back to you.

Thanks again !

<!-- gh-comment-id:3707388825 --> @dextmorgn commented on GitHub (Jan 3, 2026): Hey @NoName57, Thanks for raising this issue. Indeed, I considered usernames to be single string format. But the current validation is too strict and doesn't support your case, which I didn't consider. I'll review the username validation and come back to you. Thanks again !
Author
Owner

@dextmorgn commented on GitHub (Jan 3, 2026):

fixed with 3b4f85f66afc6f20770ef599ed804d9b441d4985.

<!-- gh-comment-id:3707419917 --> @dextmorgn commented on GitHub (Jan 3, 2026): fixed with [3b4f85f66afc6f20770ef599ed804d9b441d4985](https://github.com/reconurge/flowsint/commit/3b4f85f66afc6f20770ef599ed804d9b441d4985).
Author
Owner

@NoName57 commented on GitHub (Jan 4, 2026):

Awesome, thank you. I like the quick response. Keep up the great work!

<!-- gh-comment-id:3708464547 --> @NoName57 commented on GitHub (Jan 4, 2026): Awesome, thank you. I like the quick response. Keep up the great work!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/flowsint#1037