[PR #2931] [MERGED] chore: restore default vscode build task #5483

Closed
opened 2026-03-23 22:18:56 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/2931
Author: @richardshiue
Created: 7/4/2023
Status: Merged
Merged: 7/5/2023
Merged by: @LucasXu0

Base: mainHead: vscode-default-build


📝 Commits (1)

  • df90c4f chore: restore default vscode build task

📊 Changes

1 file changed (+2 additions, -5 deletions)

View changed files

📝 frontend/.vscode/tasks.json (+2 -5)

📄 Description

Restore the default build task to AF: Code Gen instead of both AF: Generate Freezed Files and Code Gen

Feature Preview


PR Checklist

  • My code adheres to the AppFlowy Style Guide
  • 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/2931 **Author:** [@richardshiue](https://github.com/richardshiue) **Created:** 7/4/2023 **Status:** ✅ Merged **Merged:** 7/5/2023 **Merged by:** [@LucasXu0](https://github.com/LucasXu0) **Base:** `main` ← **Head:** `vscode-default-build` --- ### 📝 Commits (1) - [`df90c4f`](https://github.com/AppFlowy-IO/AppFlowy/commit/df90c4f641991fd77305948b353ef9fe1837506b) chore: restore default vscode build task ### 📊 Changes **1 file changed** (+2 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `frontend/.vscode/tasks.json` (+2 -5) </details> ### 📄 Description Restore the default build task to AF: Code Gen instead of both AF: Generate Freezed Files and Code Gen ### 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 the [AppFlowy Style Guide](https://appflowy.gitbook.io/docs/essential-documentation/contribute-to-appflowy/software-contributions/submitting-code/style-guides) - [ ] 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 22:18:56 +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#5483
No description provided.