Releases: fsbolero/Bolero
Version 0.24.39
-
#347 Add Blazor Interactive Render Modes.
-
IServiceCollection.AddBoleroComponents()
to be called instead ofIServiceCollection.AddBoleroHost()
to use interactive render modes.
When that is used,boleroScript
will includeblazor.web.js
instead ofblazor.server.js
orblazor.webassembly.js
. -
BoleroRenderModeAttribute
can be used to indicate the render mode of the component it is applied to. -
Alternately,
Bolero.Server.Html.attr.renderMode
can be used to indicate the render mode of the component it is applied to.
-
-
Add
Program.mkStreamRendering
andProgram.mkSimpleStreamRendering
functions. -
Add
StreamRenderingComponent
base class with membersInitialModel: 'model
andLoadModel: 'model -> Task<'model>
. -
#279 Re-enable the generation of reference assemblies.
-
#355 Fix CSS isolation on rebuild.
-
Fix AttributeTargets for
EndPoint
andWildcard
.
Version 0.24
-
#347 Add Blazor Interactive Render Modes.
-
IServiceCollection.AddBoleroComponents()
to be called instead ofIServiceCollection.AddBoleroHost()
to use interactive render modes.
When that is used,boleroScript
will includeblazor.web.js
instead ofblazor.server.js
orblazor.webassembly.js
. -
BoleroRenderModeAttribute
can be used to indicate the render mode of the component it is applied to. -
Alternately,
Bolero.Server.Html.attr.renderMode
can be used to indicate the render mode of the component it is applied to.
-
-
Add
Program.mkStreamRendering
andProgram.mkSimpleStreamRendering
functions. -
Add
StreamRenderingComponent
base class with membersInitialModel: 'model
andLoadModel: 'model -> Task<'model>
. -
#279 Re-enable the generation of reference assemblies.
-
#355 Fix CSS isolation on rebuild.
Version 0.24
-
#347 Add Blazor Interactive Render Modes.
-
IServiceCollection.AddBoleroComponents()
to be called instead ofIServiceCollection.AddBoleroHost()
to use interactive render modes.
When that is used,boleroScript
will includeblazor.web.js
instead ofblazor.server.js
orblazor.webassembly.js
. -
BoleroRenderModeAttribute
can be used to indicate the render mode of the component it is applied to. -
Alternately,
Bolero.Server.Html.attr.renderMode
can be used to indicate the render mode of the component it is applied to.
-
-
Add
Program.mkStreamRendering
andProgram.mkSimpleStreamRendering
functions. -
Add
StreamRenderingComponent
base class with membersInitialModel: 'model
andLoadModel: 'model -> Task<'model>
. -
#279 Re-enable the generation of reference assemblies.
-
#355 Fix CSS isolation on rebuild.
Version 0.24.25-beta
-
#347 Add Blazor Interactive Render Modes.
-
IServiceCollection.AddBoleroComponents()
to be called instead ofIServiceCollection.AddBoleroHost()
to use interactive render modes.
When that is used,boleroScript
will includeblazor.web.js
instead ofblazor.server.js
orblazor.webassembly.js
. -
BoleroRenderModeAttribute
can be used to indicate the render mode of the component it is applied to. -
Alternately,
Bolero.Server.Html.attr.renderMode
can be used to indicate the render mode of the component it is applied to.
-
-
#279 Re-enable the generation of reference assemblies.
Version 0.23.52 (patch)
-
#336 Fix support for scoped CSS in HTML templates.
This fix disables an optimization that keeps part of the template content as plain HTML. A new static parameter
optimizePlainHtml: bool
has been added to the type provider to enable this optimization, with the inconvenient of being incompatible with scoped CSS.
Version 0.23.49 (patch)
Version 0.23.46 (patch)
- #330 Fix Bolero.Html not compiled for net8.0. Thanks @landy!
- #332 Use .NET 8 SDK RTM. Thanks @xperiandri!
- Fix mismatch between the version of FSharp.SystemTextJson required by the NuGet package and the version referenced by the assemblies.
Version 0.23
-
#308 Add router functions to decide what to do when the URL is invalid.
-
Router.withNotFound
takes an endpoint to redirect to, and applies to aRouter<_, _, _>
(ie. an inferred router). -
Router.withNotFoundMsg
takes an Elmish message to send, and applies to anyIRouter<_, _>
(including manual routers).
These functions apply when the initial URL is invalid, or when the URL is programmatically changed to be invalid.
They do not apply when the user clicks a link to an invalid URL, in order to allow external links. -
-
#309 Add support for query parameters in inferred routing with
EndPointAttribute
.-
?paramName={fieldName}
adds query parameterparamName
corresponding to the union field namedfieldName
. This parameter is mandatory iffieldName
is a string, boolean or number, and optional if it is an option or voption of these types. -
?{paramName}
is short for?paramName={paramName}
.
-
-
#313 Improve C# compatibility of server-side APIs.
For the following extension methods:IServiceCollection.AddBoleroHost
IServiceCollection.AddBoleroRouting
IEndpointRouteBuilder.MapFallbackToBolero
The following changes are applied:
- Optional arguments are changed from F#-style to C#-style. This is a source breaking change for callers who use explicit syntax
?argument = optionValue
. - Function arguments are changed from F#-style functions to C#-style
Func
orAction
.
-
#315 Support adding hash component to routing URLs:
-
Manually adding
+ "#foo"
to a routed URL will correctly scroll to the element namedfoo
in the target page. -
Methods
IRouter.Link
andIRouter.HRef
take a new optional argumenthash: string
to link to the corresponding#hash
in the target page.
-
-
#316 Fix
on.stopPropagation
andon.preventDefault
to take event names without theon
prefix, for consistency withon.event
. -
#317 Fix .NET 8 compatibility of the MSBuild task for scoped CSS.
-
#317 Fix .NET 8 compatibility of the server-side rendering of nodes.
-
#323 Use
WheelEventArgs
for wheel events andErrorEventArgs
foron.error
.
Version 0.22.45 (patch)
- #305 Ensure that CSS scopes are re-generated after upgrading Bolero.Build.
Version 0.22.44 (patch)
Fix generated name of CssScopes.