Skip to content

Conversation

@Raezil
Copy link
Member

@Raezil Raezil commented Dec 3, 2025

No description provided.

@Raezil Raezil merged commit b44d83f into main Dec 3, 2025
1 check failed
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +41 to +44
message UploadAvatarReply {
string user_id = 1 [(graphql.field) = {name: "userId"}];
uint64 size = 2;
}

Choose a reason for hiding this comment

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

P1 Badge Sizes returned as numbers despite String schema

The new upload mutations return uint64 sizes (UploadAvatarReply.size/UploadAvatarsReply.sizes), but the schema builder still exposes all 64‑bit integers as GraphQL String to avoid precision loss. At runtime prost_value_to_graphql converts Value::U64 to a numeric GqlValue, so calling uploadAvatar/uploadAvatars will advertise a String field in introspection yet emit JSON numbers, violating the declared type and risking client parsing errors. Please align the serialization with the declared string type before shipping the upload responses.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants