Skip to content

Project Symptoms (related to practice session #9) #15

@jihoonrf

Description

@jihoonrf

Below are which must be considered and applied to our all project codes for following reasons.
(1) For our team-based working to be more effective and clear
(2) To easily manage our codes(or other files, too) when we want to scaling up the project

  1. Code Style
  • Formatting:

    • Use ESLint + Prettier
  • Naming Convention:

    • UpperCamelCase for Classes in frontend side

    • lowerCamelCase for normal variables or functions in frontend side

    • snake_case for backend side

  1. Directory Structure
    Currently, there are directories named component and container for our frontend component.
    Must be changed to a structure that each directory exists per one big feature and the directory contains all related files to it.

e,g.)

  • Club

    • ClubMain
    • ClubDetail
    • ClubCard
  • Somoim

    • SomoimMain
      ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions