[PR #7432] [MERGED] fix: potential issues with displaying CircleAvatar #7882

Closed
opened 2026-03-23 23:21:36 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/7432
Author: @asjqkkkk
Created: 2/28/2025
Status: Merged
Merged: 3/3/2025
Merged by: @LucasXu0

Base: mainHead: fix/avator


📝 Commits (1)

  • 8e40acc fix: potential issues with displaying CircleAvatar

📊 Changes

1 file changed (+8 additions, -9 deletions)

View changed files

📝 frontend/appflowy_flutter/lib/workspace/presentation/widgets/user_avatar.dart (+8 -9)

📄 Description

Fix the issue of the UserAvatar component not displaying network images as circular.

Feature Preview


PR Checklist

  • My code adheres to AppFlowy's Conventions
  • I've listed at least one issue that this PR fixes in the description above.
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/AppFlowy-IO/AppFlowy/pull/7432 **Author:** [@asjqkkkk](https://github.com/asjqkkkk) **Created:** 2/28/2025 **Status:** ✅ Merged **Merged:** 3/3/2025 **Merged by:** [@LucasXu0](https://github.com/LucasXu0) **Base:** `main` ← **Head:** `fix/avator` --- ### 📝 Commits (1) - [`8e40acc`](https://github.com/AppFlowy-IO/AppFlowy/commit/8e40acc0121d89fd16ceb6c42543c79b9ffab0b5) fix: potential issues with displaying CircleAvatar ### 📊 Changes **1 file changed** (+8 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `frontend/appflowy_flutter/lib/workspace/presentation/widgets/user_avatar.dart` (+8 -9) </details> ### 📄 Description Fix the issue of the `UserAvatar` component not displaying network images as circular. ### Feature Preview <!--- List at least one issue here that this PR addresses. If it fixes the issue, please use the [fixes](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) keyword to close the issue. For example: fixes https://github.com/AppFlowy-IO/AppFlowy/pull/2106 --> --- <!--- Before you mark this PR ready for review, run through this checklist! --> #### PR Checklist - [x] My code adheres to [AppFlowy's Conventions](https://docs.appflowy.io/docs/documentation/software-contributions/conventions) - [x] I've listed at least one issue that this PR fixes in the description above. - [x] I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes. - [x] All existing tests are passing. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
mirror 2026-03-23 23:21:36 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#7882
No description provided.