[PR #5163] [MERGED] feat: use font name instead of fontname_regular #6677

Closed
opened 2026-03-23 23:16:10 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/5163
Author: @LucasXu0
Created: 4/19/2024
Status: Merged
Merged: 4/29/2024
Merged by: @LucasXu0

Base: mainHead: font_name


📝 Commits (2)

  • afa5faa feat: use font name instead of name_regular
  • 9f4e2e2 Merge branch 'main' into font_name

📊 Changes

3 files changed (+15 additions, -9 deletions)

View changed files

📝 frontend/appflowy_flutter/lib/plugins/document/presentation/editor_plugins/mobile_toolbar_v3/aa_menu/_font_item.dart (+1 -2)
📝 frontend/appflowy_flutter/lib/plugins/document/presentation/editor_style.dart (+12 -4)
📝 frontend/appflowy_flutter/lib/workspace/presentation/settings/widgets/settings_appearance/font_family_setting.dart (+2 -3)

📄 Description

Feature Preview

Previously, we were using 'fontname_regular' as the value for the font key, but it could not be parsed on the web. Now, we are using the real font name instead of 'fontname_regular'.

For example, 'ADLaMDisplay_regular' should be 'ADLa MDisplay'.


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/5163 **Author:** [@LucasXu0](https://github.com/LucasXu0) **Created:** 4/19/2024 **Status:** ✅ Merged **Merged:** 4/29/2024 **Merged by:** [@LucasXu0](https://github.com/LucasXu0) **Base:** `main` ← **Head:** `font_name` --- ### 📝 Commits (2) - [`afa5faa`](https://github.com/AppFlowy-IO/AppFlowy/commit/afa5faa28b920c0bccbb69d383e94b0e603af825) feat: use font name instead of name_regular - [`9f4e2e2`](https://github.com/AppFlowy-IO/AppFlowy/commit/9f4e2e260e29ebb4fb82de1ecb3c6eab22df6a8e) Merge branch 'main' into font_name ### 📊 Changes **3 files changed** (+15 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `frontend/appflowy_flutter/lib/plugins/document/presentation/editor_plugins/mobile_toolbar_v3/aa_menu/_font_item.dart` (+1 -2) 📝 `frontend/appflowy_flutter/lib/plugins/document/presentation/editor_style.dart` (+12 -4) 📝 `frontend/appflowy_flutter/lib/workspace/presentation/settings/widgets/settings_appearance/font_family_setting.dart` (+2 -3) </details> ### 📄 Description <!--- Thank you for submitting a pull request to AppFlowy. The team will dedicate their best efforts to reviewing and approving your pull request. If you have any questions about the project or feedback for us, please join our [Discord](https://discord.gg/wdjWUXXhtw). --> <!--- If your pull request adds a new feature, please drag and drop a video into this section to showcase what you've done! If not, you may delete this section. --> ### Feature Preview Previously, we were using 'fontname_regular' as the value for the font key, but it could not be parsed on the web. Now, we are using the real font name instead of 'fontname_regular'. For example, 'ADLaMDisplay_regular' should be 'ADLa MDisplay'. <!--- 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) - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
mirror 2026-03-23 23:16:10 +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#6677
No description provided.