Skip to content
GitHub Explorer

Kern000/projectTwoBackendServer

View on GitHub ↗Related repositories →

backend server with layer architecture using mongoose schema, router layer, controller, service layer, with data access layer being encapsulated within service layer

active 2023-08-15 → 2023-10-17 (UTC)

Complete coverage26,730 / 26,730 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-01 (UTC)
Events
93
Pushes
61
Pull requests
0
Issues
15
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 64 days from 2023-08-15 to 2023-10-17. Pushes: 61 total, peak 28 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 15 total, peak 8 in a day. Comments: 16 total, peak 12 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
Kern0008161013
edisonzsq11003

Recent activity

Latest issues, pull requests and releases

  • Issue#8Kern0002023-10-13 08:52
    Validate request data
  • Issue comment#8Kern0002023-10-13 08:52
    Validate request data
  • Issue comment#6Kern0002023-10-13 08:52
    Handle more alternate flows
  • Issue#6Kern0002023-10-13 08:52
    Handle more alternate flows
  • Issue#7Kern0002023-10-13 08:49
    Logging for traceability
  • Issue comment#7Kern0002023-10-13 08:49
    Logging for traceability
  • Issue#8edisonzsq2023-09-20 11:32
    Validate request data
  • Issue#7edisonzsq2023-09-20 11:31
    Logging for traceability
  • Issue#6edisonzsq2023-09-20 11:31
    Handle more alternate flows
  • Issue comment#5Kern0002023-09-20 01:19
    Marking Feedback
  • Issue#5edisonzsq2023-09-19 23:29
    Marking Feedback
  • Issue#1Kern0002023-08-15 06:46
    Naming is not intuitive and confusion with User Schema
  • Issue comment#1Kern0002023-08-15 06:46
    Naming is not intuitive and confusion with User Schema
  • Issue comment#3Kern0002023-08-15 04:44
    Not handling enough alternate flow and understanding of http status
  • Issue#3Kern0002023-08-15 04:44
    Not handling enough alternate flow and understanding of http status
  • Issue#4Kern0002023-08-15 04:43
    Consider improving your API design
  • Issue comment#2Kern0002023-08-15 04:43
    Where should you catch error?
  • Issue#2Kern0002023-08-15 04:43
    Where should you catch error?
  • Issue comment#1edisonzsq2023-08-15 03:15
    Naming is not intuitive and confusion with User Schema
  • Issue comment#3edisonzsq2023-08-15 03:13
    Not handling enough alternate flow and understanding of http status
  • Issue comment#2edisonzsq2023-08-15 03:11
    Where should you catch error?
  • Issue comment#4Kern0002023-08-15 02:48
    Consider improving your API design
  • Issue comment#3Kern0002023-08-15 02:46
    Not handling enough alternate flow and understanding of http status
  • Issue comment#3Kern0002023-08-15 02:44
    Not handling enough alternate flow and understanding of http status
  • Issue comment#2Kern0002023-08-15 02:43
    Where should you catch error?

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.