[Snyk] Upgrade ol from 9.0.0 to 9.2.4 #2
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.
This PR was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade ol from 9.0.0 to 9.2.4.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 134 versions ahead of your current version.
The recommended version was released on 2 months ago.
Release notes
Package name: ol
The 9.2.4 is a patch release that addresses the issue below.
The 9.2.3 is a patch release that addresses the issue below.
The 9.2.2 is a patch release that addresses the issues below.
List of all changes
The 9.2.1 release patches the 9.2.0 release with a fix for a TypeScript issue using vector layers.
List of all changes
See below for a complete list of features and fixes.
The 9.2 release fixes a number of rendering issues and introduces a few new features. OGC tile sources now support collections selection. Snap events are now more consistent (see below). Type annotations continue to improve, and documentation and examples got a number of updates.
The
snap
event's feature property is now nevernull
Previously, listeners for the
Snap
interaction'ssnap
event receivednull
as value for thefeature
property when snapped to a segment. Now, the value of thefeature
property is always set to the snapped feature.To distinguish between a vertex and a segment snap, look at the
snap
event'ssegment
property. It will set tonull
on a vertex snap, and to the snapped segment on a segment snap.List of all changes
See below for a complete list of features and fixes.
Dependency Updates
New Contributors
Full Changelog: v9.1.0...v9.2.0