Jeffrey T. Fritz

REALLY cool addition to the workshop, and we would definitely like to take the upgrade to .NET 6 I'm going to do a .NET 6 upgrade and docs update separately....

Yes, I think we need to roll-back the initial requirements attributes in Address.cs as a recommended fix to this

Yes, and I struggled with them for 3 hours. They are not linked on the homepage of this repository, it was very hard to find and does not cover the...

I like the idea of a configuration option, but I think if localStorage isn’t available, developers should have an appropriate exception thrown Jeff > On Aug 27, 2022, at 18:43,...

I'm referring to an exception if AppSettings is inaccessible and the In-Memory fallback is not enabled. "AppSettingsUnavailableException" or similar

Yes, in a WebAssembly scenario all context is lost when the app is reloaded. For users who are privacy concerned, this should be a fair consideration in exchange for not...

I'm observing that the ItemsProvider isn't triggered for additional data until the next batch of data would be presented on screen. Should the ItemsProvider be called before the Overscan items...

After thinking and investigating, the issue appears to be at https://github.com/dotnet/aspnetcore/blob/main/src/Components/Web/src/Virtualization/Virtualize.cs#L170 The observers in the TS file are being initialized with a reference to the spacer element, which is located...

I am now running into this issue whenever I open VSCode and work on my project in Linux. The workaround that I found is this: https://stackoverflow.com/questions/43469400/asp-net-core-the-configured-user-limit-128-on-the-number-of-inotify-instance

I’ll clarify: on Win10 fall creators update it doesn’t position the output on secondary screens