Maksym Koshovyi

My manual implementation looks like this: Usage: ```cs public async Task GetUsersAsync(IEnumerable userIds) { var request = await GetBaseRequestAsync(); var response = await request .AppendPathSegment("user/getUsers") .PostJsonAsync(new { UserIds = userIds.ToArray()...

The goal is to bring `DateOnly` and `TimeOnly` more in line with `DateTime` (since they are basically subsets of that type). This does work: ```cs var dateTime = TypeDescriptor.GetConverter(typeof(DateTime)).ConvertFromString("01.01.0001"); ```...

I think, that's the limitation of `System.Text.Json` serializer: https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-supported-collection-types?pivots=dotnet-6-0#supported-key-types But I'll take a look if I can do anything about it.

Cool idea! But it might be out of the scope for this package. The goal here is to compensate for lacking support for `DateOnly` and `TimeOnly` in ASP.NET Core 6....

Possible implementation: 1) Add events from whole semester to the calendar 2) Implement #18, and update only changed events in the calendar Questions: - What if user updates their filter?...

@Felkree this notification can only be sent AFTER update (how else can I compare old and new timetable). So for now, you'll need to trigger update by yourself, and after...

@Felkree yes, but notification by itself will be useful too. You won't need to check timetable for changes after update this way

> first you need to make the division in the application into classes (i.e. from 7:45 to 9:20, etc.) This is a separate issue. Please refer to #25 for further...

Any updates on this? This has been marked as `in-progress champion` for three months now, I think

In the meanwhile you can use [WeakSubscribe](https://github.com/xamarin/XamarinCommunityToolkit/blob/main/src/CommunityToolkit/Xamarin.CommunityToolkit/ObjectModel/Extensions/INotifyPropertyChangedExtension.shared.cs#L10) as a workaround. It acomplishes the same thing as ObservableObject with WeekEventManager underneath. It's marked as Obsolete because XCT already has ObervableObject with...