Date | 2025-07-01 (15 days ago) |
---|---|
NuGet | View on NuGet |
GitHub | View on GitHub |
Target Frameworks | .NET 8 |
Umbraco Versions | Umbraco 13 |
New alpha release for Umbraco 13 🎉
#installation
">InstallationInstall via NuGet - either via the .NET CLI:
dotnet add package Limbo.Umbraco.Spa --version 13.0.0-alpha009
or the NuGet Package Manager:
Install-Package Limbo.Umbraco.Spa -Version 13.0.0-alpha009
#changelog
">ChangelogThe InitSite
method should exit right away if a previous step has already set a current site node (see 3d0a0e5
)
When extending the SpaRequestHelper
class, a previous step may set the request.Site
property. If this is the case, the SpaRequestHelper.InitSite
method should overwrite the value.
Updated the SpaRequestHelper.ReadFromCache
to set the culture of the current thread (see ab09350
)
When retrieving a SpaCachedModel
from the SPA's micro cache, the culture of the current thread was being set, potentially causing (parts of) responses to be based on on the wrong culture.
Updated the logic behind the SpaRequestOptions.EnableCaching
property (e868135
)
Previously the value couldn't be overridden through the query string when running the site in development mode. With this commit, this is now possible, but caching is disabled by default (opposed to enabled by default when not in development mode).