API-23: Refactoring for better architecture (#12)

Endpoints are separated into distinct packages and interfaces are extracted into files

Co-authored-by: Patrick Müller <patrick@mueller-patrick.tech>
Reviewed-on: #12
Co-authored-by: Patrick Müller <patrick@plutodev.de>
Co-committed-by: Patrick Müller <patrick@plutodev.de>

src/models/partyplaner/PartyPlaner.router.ts

@@ -2,10 +2,14 @@
  * Required External Modules and Interfaces
  */
 import express, {Request, Response} from 'express';
-import {dataRouter} from './data/Data.router';
 import {registerRouter} from './register/Register.router';
 import logger from '../../middleware/logger';
 import {loginRouter} from './login/Login.router';
+import {userRouter} from './user/User.router';
+import {eventRouter} from './event/Event.router';
+import {friendshipRouter} from './friendship/Friendship.router';
+import {inviteRouter} from './invite/Invite.router';
+import {sessionRouter} from './session/Session.router';
 
 /**
  * Router Definition
@@ -13,9 +17,13 @@ import {loginRouter} from './login/Login.router';
 export const partyPlanerRouter = express.Router();
 
 // Sub-Endpoints
-partyPlanerRouter.use('/data', dataRouter);
-partyPlanerRouter.use('/register', registerRouter);
+partyPlanerRouter.use('/event', eventRouter);
+partyPlanerRouter.use('/friendship', friendshipRouter);
+partyPlanerRouter.use('/invite', inviteRouter);
 partyPlanerRouter.use('/login', loginRouter);
+partyPlanerRouter.use('/register', registerRouter);
+partyPlanerRouter.use('/session', sessionRouter);
+partyPlanerRouter.use('/user', userRouter);
 
 partyPlanerRouter.get('/', async (req: Request, res: Response) => {
     try {