pckv/kompis

kompiskjøring

kompis's Issues

Add a CI solution

Delete users listings when deleting a user

When a user is deleted all their listings must be deleted as well. At the moment deleting a user with existing listings results in foreign key constraint.

Implement location of a listing in backend

Add @Autowired to all bean constructors

Cleanup user controller and service

• Remove endpoints that are not needed
• Add checks where needed (such as existing email when making a new user)
• Use user object instead of id
• Endpoints like delete should be done on the logged in user, not on a specified user / id

Codacy does not like our readme

Update API documentation for delete user

When deleting a user their listings will be deleted and they will be unassigned from all listings.

Create a Discord server for Kompis

Create a Discord server for Kompis project where we can communicate and get updates.

Document API and refactor controllers

Currently, the API is inconsistent and does not have a clear definition of how it should be used. We should plan and document the API in its entirety.

Create tests for User service

Add code quality solution

Create PostgreSQL server

Create database on the autodeploy server and set up a project user, and a user for each member of the group.

Setup automatic deployment from master branch to dev server

Implement login system with JSON web token

service and controller will need the following functionality:

• Create user
• Login, which adds the JSON web token as a response and returns the user object
• Get the current logged in user
• Logout?

Create mock MVC testing for login system

Create location class

Create a location class that stores latitude, longitude and accuracy.

Set up maven project

Fix inconsistencies in the API documentation and controllers

• /users/authorize → documentation missing 404 and 403. Remove 409

• /users/{id} → returns 409 instead of 404

• /users/current → documentation missing 404

• /listings/{id}/unassign → typo: replace 409 with 403

• Add 403 documentation for all /listings endpoints

Tokens for deleted users are still valid

Add response messages to ResponseStatusException throw cases

Create Listing service and controller

Functionality:

• Create a new listing
• Delete a listing
• Deactivate/activate a listing
• Get a listing
• Get all listings
• Assign logged in user to a listing

Create a Listing entity and repository

A listing can be made either as a driver, or as a passenger. The following attributes are required

• boolean for 'as a driver' or 'as a passenger'
• location (either two fields as latitude and longitude or a proper data class with math support)
• title
• description
• owner
• assignee (for driver listings, assignee will be the passenger and vice versa)

Connect GitHub repo to Discord with webhook

Validate fields in entities

Known issues:

• Listing can be created with no title
• Users can be created with no email, password and display name

Set up autodeploy server

Set up a VM with SSH authentication for all members of the group.

Create AttributeResolver for Listing objects

Listing functions should look like the following after this implementation:

@GetMapping("/{listingId}")
public Listing getListing(Listing listing) {
}

Create tests for ListingService

Create readme

Create a readme with some information about the project.

Create User entity and repository

A user has the following attributes:

• email
• password
• displayname

Create license file

Create User service and controller

Functionality:

• Create a user
• Get user entity