Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
jihoonrf opened this issue Oct 31, 2019 · 0 comments
Open

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

jihoonrf opened this issue Oct 31, 2019 · 0 comments
Labels

Comments

@jihoonrf
Copy link
Contributor

jihoonrf commented Oct 31, 2019

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
      ...
@jihoonrf jihoonrf pinned this issue Nov 25, 2019
@jihoonrf jihoonrf added the tip label Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant