Yelp Against Companies

This is a joke webapp that makes fun of the whole employment situation..

Workflow/Action is currently:

Raison d être

This app is based on a recurring joke in unemployment circles on how employees should be able to judge employers/companies on how the former is treated by the latter. Apparently I was not the only one to think of this as sites like glassdoor.com already exist. By doing so employees would warn each other not to waste time with certain employers and or companies.

Functionality

The frontend would be like a forum where visitors could click on the name of a company which would open up a new page of the company with an itemized list of comments by user, including individual ratings. With every new comment and rating the average rating of the company is updated. To make a new company/comment and rate companies employees should be logged in. To see the ratings and companies users do not need to be logged in.

Problems (and how I solved them)

• Problems with entity framework (migrations, relationships, seeding, etc.) => Solving issues with the Guid had me delete the established database and migrations and start anew. I also needed a minute to remember how to properly set up relations by using eager loading.
• Problems with a singular component in angular requiring miltiple endpoints of the api to retrieve the relevant data, because they are async data does not load properly into the html. => For now I have one function to get the ratings inside the function to get the company, but it is an ugly solution, so maybe later make a new endpoint that actually retrieves the data in a single json to match the single angular component.
• Somehow I got an error with registering new users, but they did end up in the database anyway... => turns out that I should have added the line .AddDefaultTokenProviders() to the DI.
• Problems with telling the user proper information. Tried to do a popup in angular, but I have been unable to make that work. For now I will simply use html that appears based on *ngIf.
• The Api returning errors (like 400) to Angular needs to be caught in a different way. There was a lot of trial and error here but I think I am on the right way with the catchError pipe.
• Spend half a day wondering why an http method in Angular did not work to send the data to the API. Finally noticed the missing "/" in the urlstring. Always check the strings...
• Never quite figured out why Lazy loading of the ef entities did not work untill I saw that I was not using LazyLoadingProxies. Now lazy loading works.