Releases: ljbc1994/BlazorIntersectionObserver
Releases · ljbc1994/BlazorIntersectionObserver
3.1.0: Resolving JS asset location for relative paths
3.0.1: Helpful error messages for `IntersectionObserve` component
Helpful error messages will now appear if the consumer fails to provide:
- An element to observe.
- No element within the component.
3.0.0: Namespace update to avoid conflicts with Blazor libraries
- Namespace has been changed to
Ljbc1994.Blazor.IntersectionObserver
to avoid namespace conflicts with Blazor libraries. - Bump to node packages to avoid security vulnerabilities
2.0.3: Include unminified js script
- This release now outputs both the unminified and minified versions for the js script.
Missing changes to csproj
- Added references to the csproj for the new minified js file.
Improvements to the component and API
IntersectionObserve
now requires a reference to the node it's observing, means the component only deals with observing and not polluted withClass
orStyle
.
Now the component's context includes a reference which needs to be provided with the element that needs to be observed.
@using Blazor.IntersectionObserver
<IntersectionObserve>
<div @ref="context.Ref.Current">
Hey... I'm @(context.IsIntersecting ? "in view": "out of view")
</div>
</IntersectionObserve>
- A new
dispose
method on the service rather thandisconnect
.Disconnect
follows the API and removes any elements that are being observed but does not remove the observer. - Remove underlying shared observer, instead each
IntersectionObserve
instance will have their own observer. - Updates to documentation to reflect the above changes.
- Include a minified script file for js import.
- Bump outdated npm packages.
Updated package to remove content files
- Removed content files bleeding into the nuget package build.
Upgraded to dotnet 5
What's the update?
- This package now works with dotnet 5 for both webassembly and server.