johansaisa / gt Goto Github PK

• Add property in listing entity and DTO for last application date, id for company logo image
• Review which properties should be unique (e.g. Location Name)
• Review which properties should be nullable (e.g. FilterDTO)
• Update properties with appropriate annotations
• Find solution for FK restraint which keeps the database from deleting a Listing if a ListingInquiry has a FK referencing the Listing.
• Add LinkedIn link to ApplicationUser ?
• Migrate database(s)

Users should be able to go to a page and then see a list of listings. This should be scrollable loading in a new set amount listings

Implement a base layout for the website.

Create a User data seeder to baseline some dummy data in the Identity Database

Add Mapper and configure mapper to currently existing base entities.

• Add implementations of Services
• Add implementations of Repositories
• Add implementations to DI

Add the #NULLABLE DISABLE to the different DB Entity classes to disable warning messages in output.

Change the base / root folder to SRC to follow naming convention.

• Add GTAppContext DbSets
• Add Migration

Remove github action ubuntu workflow to save on free minutes for the public repository.

• FirstName
• LastName
• New Migration

The following bugs have been identified in ListingService.cs:

When creating a new listing:

• The property CreatedDate is always null

When updating a listing: 

• Keeps old company and does not create and assign a new. 
• Experience level gets added to the db but id is not applied to the updated listing.

When deleting a listing:

• Does not work with listings which have a connected ListingInquiry. Appears to be a problem with cascading delete.
  The DELETE statement conflicted with the REFERENCE constraint "FK_ListingInquiries_Listings_ListingId". The conflict occurred in database "GTAppDb", table "dbo.ListingInquiries", column 'ListingId'.

When calling the GetAsync() method using the filter:

• Does not filter by jobtitle
• Keywords filter property do not search for matches in listingTitle, Employer, ExperienceLevel
• ExperienceLevels filter property do not filter by anything. Always returns everything
• Shows no results when Location is set to an empty string in JSON. All other paramaters can be set to an empty string in JSON ("").

    //Returns nothing when passed in as JSON input:
    "Location" : ""
    
    //Returns all matches when passed in as JSON input:
    "fte": "",
    "salaryMin": "",
    "salaryMax": "",
    "ExperienceLevels" : [],
    "jobTitle" : ""

Create database seeder for application dummy data.

Draft skeleton for UI with menu item links to predefined pages.

Through API controllers. Testing with postman is enough for now since this will work with SPA later

This issue and branch will most likely remain open for the duration of the group project.

Connected to #75. Continue in separate issue as merge to main was necessary on decision to redesign (View-pages instead of Razor-pages).

Address should not be connected to an company.

Create base line project structure for N-tier architecture

Users should be able to step into a listing to see all available information about the listing. Further development should contain button to make listing inquire etc