• Project I made to practice Clean Architecture (Robert C. Martin ) and thin Controllers using MediatR with ASP.NET MVC

• Fronted is made with the Vue composition API and script setup

• Demo app on heroku hobby dev (so takes a while to load):https://dotnet-vue-issue-tracker.herokuapp.com

• Add possibility to share your project / issue with another user.
  • share button > fill in user email > if email exists in DB > user gets invitation > upon accepting > project / issues gets pushed to his DB
  • When you share an issue, the other user can write comments in the description (link a different font color to the other user)
  • add possibility to add other users to the project, when you initially create the project
• Link issues to github commits
• Add possibility to add Screenshots to your issue Description
• Make a mobile version or make mobile friendly
• EF inserts data in random order. Write an algorithm to keep track of the current position of the issue in the table
  • for example: if the isssue is an openIssue, store the index off the issue in the openIssue array in the backend
  • upon fetching the openIssues => insert issue in the arr at [index]

• Make sure you have PostGress installed on your pc, create a DB for your project and Change the ConntectionString in /WebUI/appsettings.Development.json
  • "ConnectionStrings": { "DefaultConnection": "Server=localhost; Port=5432;User ID=jan; Password=xxxx; Database=issue_tracker_db; Pooling=true;" }
  
  

There is an issue(at the time of writing), where EF Core doesn't create the DB automatically for you when your DB is Postgress.

- cd into Client folder 
    - $ pnpm install 
    - $ npm run dev

- cd into WebUI folder
    - $ dotnet run

• when you run '$ dotnet run', seed (dummy) data gets stored into your db, so you have something to work with
  • check Infrastructure/Persistence/Seed.cs

• This project is a continuation of my former issue-tracker repo https://github.com/JDN89/issue-tracker-discontinued .
  Github was not displaying my commits in my activity graph (that's why there is a gap in 02/2022 and 03/2022).
  The only solution I found was creating a new repo (this one) and cloning my old repo into this one.