- Updated
Giraffe
dependency to5.0.0-rc-6
and changed fromTaskBuilder.fs
toPly
fortask
CEs.
- Upgraded to .NET 5
- Added an overload to the
AddRazorEngine
extension method to set if existing file providers should be kept or cleared via thepersistFileProviders
flag.
- Dropped support for all .NET framework monikers except .NET Core 3.1 (in preparation for the .NET 5 release)
- Added support for
IModelMetadataProvider
- Fixed a bug around the
TempData
implementation to ensure that all previously stored data in theTempData
dictionary is accessible as well as newly made changes are persisted going forward.
- Added an additional overload of
AddRazorEngine
which does not take any arguments, which supports Razor views from a class library.
- Added a new parameter to the
razorView
,razorHtmlView
, andRazorEngine.renderView
functions to support aModelStateDictionary
.
- Added support for view data in the
razorView
andrazorHtmlView
http handlers
- Upgraded to Giraffe 3.2.*
- Upgraded to latest TaskBuilder.fs
- Added
charset=utf-8
to theContent-Type
header when callingrazorHtmlView
Upgraded to Giraffe 2.0.0
and the latest ASP.NET Core 2.1.*
NuGet packages.
Added support for view folders (see #1, #3).
Upgraded to Giraffe 1.1.0
.
Changed copyright notice in NuGet package.
Upgraded to latest Giraffe 1.0.0
release.
Upgraded to latest Giraffe 0.1.0-beta-6**
release.
Upgraded to latest Giraffe 0.1.0-beta-5**
, which has a new dependency on Giraffe.Tasks
from NuGet.
- Added
validateAntiforgeryToken
http handler for verifying anti forgery tokens.
- Renamed the
Giraffe.Razor.Engine
module toRazorEngine
and moved it under the namespaceGiraffe.Razor
. If you were using therenderRazorView
function to render individual razor views then you have to change the function call toRazorEngine.renderView
now.
(Most Giraffe users will probably not bet affected if they were using the razorView
or razorHtmlView
http handlers.)
Previous releases of this library were documented in Giraffe's release notes.