feat: Initialize Prettier and ESLint with formatting workflows - #88
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several improvements focused on project automation, code style enforcement, and documentation clarity. The main changes are the addition of GitHub Actions workflows for linting and formatting, the introduction of Prettier configuration and ignore files, and significant enhancements to the project's architecture and decision records.
Automation and Code Quality
.github/workflows/lint.yml), which runs on pull requests targetingmasterordevelopand checks code quality usingpnpm lint..github/workflows/format.yml), ensuring consistent code style by runningpnpm format:checkon relevant file changes..prettierrc.jsonand.prettierignoreto define and enforce Prettier formatting rules and specify files/directories to ignore. [1] [2]Documentation Improvements
ARCHITECTURE.md, including clearer explanations of the architecture layers, data flow, feature organization, and testing strategy. The formatting was improved for readability, and step-by-step checklists were added for feature development and testing. [1] [2] [3] [4] [5] [6]DECISIONS.mdwith additional context and improved formatting for architectural decisions, making trade-offs and motivations clearer.Minor Documentation Updates
AGENTS.mdandCLAUDE.mdfor better onboarding and development guidance. [1] [2] [3] [4] [5]These changes collectively strengthen code consistency, automate quality checks, and make the project's structure and rationale more accessible to contributors.