FluxorInBlazor: retarget net10.0, pin Fluxor.Blazor.Web 6.11.0, clear two transitive advisories - #2137
Open
vladimir-pecanac-main wants to merge 1 commit into
Conversation
… two transitive advisories Retarget both projects from net8.0 to net10.0. Bump Fluxor.Blazor.Web 5.9.1 -> 6.11.0 and the WebAssembly packages 8.0.0 -> 10.0.0. Pin AngleSharp 1.6.0 and Microsoft.Extensions.Caching.Memory 10.0.0 in the test project to clear NU1902 and NU1903, which arrived transitively via bunit. No source changes are needed: every Fluxor API the sample uses survives the major version jump unchanged. Build is 0 warnings / 0 errors and all 4 tests pass on SDK 10.0.302.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retargets
blazor-libraries/FluxorInBlazortonet10.0and brings its packages current, alongside the .NET 10 refresh of the Fluxor for State Management in Blazor article.net8.0->net10.0.Fluxor.Blazor.Web5.9.1 -> 6.11.0;Microsoft.AspNetCore.Components.WebAssemblyand.DevServer8.0.0 -> 10.0.0.AngleSharp1.6.0 andMicrosoft.Extensions.Caching.Memory10.0.0 to clear NU1902 and NU1903, which arrived transitively through bunit. Both were pre-existing and unrelated to Fluxor.No source changes were needed. Every Fluxor API the sample uses survives 5.9.1 -> 6.11.0 unchanged:
<Fluxor.Blazor.Web.StoreInitializer/>,AddFluxor()/ScanAssemblies()/AddMiddleware<T>(), and[FeatureState],[ReducerMethod],[ReducerMethod(typeof(T))],[EffectMethod(typeof(T))].The sample stays a standalone Blazor WebAssembly app, which is still a first-class supported template on .NET 10. The article's new render-mode material about Blazor Web Apps is prose and needs no sample project.
Verified on SDK 10.0.302:
dotnet build -c Release-> 0 warnings, 0 errors;dotnet test-> 4/4 passing.