Skip to content

Latest commit

 

History

History
51 lines (26 loc) · 3.1 KB

README.md

File metadata and controls

51 lines (26 loc) · 3.1 KB
Raw

ASPNETCoreWebAPIDispatcherWithEFCore

A simple ASP .NET Core Web API App which presents work of airline dispatchers using EF Core

Discription App

The airport serves flights with scheduled flights. Date / Time of departure may differ from the time of departure of the flight - for example, if the flight was delayed, the time of departure will be delayed accordingly. For the departure, the aircraft and crew are appointed. The crew consists of a pilot (1) and stewardesses (1 or more). Aircraft that belong to the airport have a service life depending on the type of aircraft and require timely maintenance.

We as dispatchers must have CRUD operations on all entities.

Classes should look like this:

  • Flights (flight number, departure point, departure time, destination, time of arrival at the destination place, tickets)

  • Ticket (Id, price, flight number)

  • Departures (Id, flight number, departure date, crew, airplane)

  • Stewardesses (Id, Name, Surname, Date of Birth)

  • Pilots (Id, Name, Surname, Date of Birth, Experience (eg 3 years))

  • Crew (Id, Pilot (1), Stewardesses (1 or more)

  • Airplane (Id, Airplane name, Airplane type, Airplane release date, TimeSpan)

  • Types of aircraft (Id, model aircraft, number of seats, load capacity (kg))

Aim of this project

Create a project ASP.NET Core WebAPI and realize endpoints which described above. Create a model for all the structure which above. Also you need add some seeds data which will download by default.

Important:

  1. Split all logic on the layer: Presentation Layer - controller, Business Layer - service, Data Access Layer - repository.

  2. Use the IoC container, that is to break all the logic into different services and create abstractions for them (all for IoC and Dependency Inversion Principle).

  3. Have two sets of classes: DTO and Model. Use mapping (you can use the AutoMapper library).

  4. Add Validation (FluentValidation library can be used if desired)

  5. To work with data, implement one of the approaches described in the lecture, or if you know something else that you think is best suited for this task. However, keep them in memory. (You do not need to implement operations with a real database!).

  6. On the basis of the previous DZ - to implement the CodeFirst approach. It is desirable to use attributes (attribute parameters - at your discretion). It is also necessary to have at least 2 migration files (for example, you can implement all the links and add the migration with the name of Init, and then arrange the attributes and add the second migration). The final solution should create a database (if it is not), apply migration files, and fill the (Seed) database with default values ​​(2-3 objects per table). Work with DbContext and DbSet should be exclusively in services (which you implemented in the previous job). Optionally, you can make a wrapper in the form of UnitOfWork and Repository (which will store DbContext inside and perform operations on DbSet).

Have fun)

"Motivation is good, but not the answer to keep you going in the long run. Become passionate about what you do."

– Yad Faeq