[GH-ISSUE #237] [Task] Add explanation of warnings in coding conventions #126

Closed
opened 2026-03-23 20:32:11 +00:00 by mirror · 1 comment
Owner

Originally created by @MikeWallaceDev on GitHub (Jan 7, 2022).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/237

Originally assigned to: @MikeWallaceDev, @appflowy on GitHub.

there must be no warnings in the development or main branches. No developer can check-in code that conttains warnings.

Originally created by @MikeWallaceDev on GitHub (Jan 7, 2022). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/237 Originally assigned to: @MikeWallaceDev, @appflowy on GitHub. there must be no warnings in the development or main branches. No developer can check-in code that conttains warnings.
Author
Owner

@MikeWallaceDev commented on GitHub (Jan 11, 2022):

Added to the Code Submission Guide

<!-- gh-comment-id:1009477268 --> @MikeWallaceDev commented on GitHub (Jan 11, 2022): Added to the Code Submission Guide
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#126
No description provided.