Skip to content

fix!: omit name, avatar_url and last_seen_at from responses when empty #18005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 23, 2025

Conversation

BrunoQuaresma
Copy link
Collaborator

User name, avatar URL, and last seen at, are not required fields so they can be empty. Instead of returning the 0 values from Go, we want to make it more agnostic, and omit them when they are empty. This make the docs and usage way clearer for consumers.

@BrunoQuaresma BrunoQuaresma requested a review from Emyrk May 23, 2025 12:24
@BrunoQuaresma BrunoQuaresma self-assigned this May 23, 2025
@BrunoQuaresma BrunoQuaresma changed the title fix!: omit name and avatar_url from responses when empty fix!: omit name, avatar_url and last_seen_at from responses when empty May 23, 2025
@github-actions github-actions bot added the release/breaking This label is applied to PRs to detect breaking changes as part of the release process label May 23, 2025
Copy link
Member

@Emyrk Emyrk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL a user can have no name, but that does make sense. Only the username is required.

@BrunoQuaresma BrunoQuaresma merged commit 94c129c into main May 23, 2025
41 checks passed
@BrunoQuaresma BrunoQuaresma deleted the bq/fix-user-response branch May 23, 2025 14:35
@github-actions github-actions bot locked and limited conversation to collaborators May 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release/breaking This label is applied to PRs to detect breaking changes as part of the release process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants