National Pedagogical Dragomanov University timetable application with telegram bot frontend

The app is built upon working solution using this as "API" _{and that api is really bad don't look at the source code and do not even try to look at what's server returns to the browser}

The core of the application. All entities that shared between other parts of the program as well as interfaces that must be implemented somewhere and could be used across the app.

Implement some common staff from Core and also managing localization.

Does the dirty stuff working with the university's server to provide handy api for getting classes. Caches some things but still serialization takes time.

For storing users with their faculty groups. Uses Ef Core for implementing DAO.

Not implemented in v3 but was working? in v2 so can be ported

Using Telegram.Bot encapsulates logic working with telegram api and provide app functionality through that. Uses separated entity to store telegram users so persistence not managed by NpuRozklad.Persistence but rather inside NpuRozklad.Telegram project. Not sure if this a good idea to split the domain user entity into two.

Ties up everything with adding logging and configuring all parts. Endpoint for telegram api webhook using asp net core

There is also tests but they are dumb and ugly _{^{like Soda}}