Luke Parker

A bit of context for on our Authentication page: ```html ``` ```cs public async void UpdateAuthenticationState() { var authState = await AuthenticationStateTask; var user = Application.User.PortalUserAccessor.MapPortalUser(authState); await FeatureFlagsClient.GetFeatureFlagsForUserAsync(); await BusinessContextService.LoadDefaultOrLocalStorageBusinessContext(user);...

Honestly - it seems to be the FluentAutocomplete covers this behaviour. But I also then feel that FluentSearch is not needed because of this. What is the main difference?

Great feature. I have this in the back of my head but put it off from no real need. Since someone actually wants this I'll try to get it into...

Yes this is 100% doable... - Up API provides the Tags on every transaction. - Up API also lets you create & assign tags using the API. I could create...

I'll have a bit of a think, then implement for you. Once its in, give it a go and let me know feedback :)

https://github.com/dotnet/aspnetcore/issues/40046

Hey, I had similar problems, but mainly with how long it took to blur from a field (approaching 800ms for a simple state update) Dev Tools is the culprut. 2...

Okay I did more testing. You can keep the stack trace & default Latency. STJ is the only change needed for my perf fix.

In my Blazor app there was a massive slowdown with default dev tool settings or explicitly saying use Newtonsoft. When I changed the serialised to use SystemTextJson it went away....

I've got some unit tests to write - however the rest should be good to go