@itwin/unified-selection
Advanced tools
@itwin/unified-selection - npm Package Compare versions
Comparing version 0.5.1 to 1.0.0
| # @itwin/unified-selection | ||
| ## 1.0.0 | ||
| ### Major Changes | ||
| - [#727](https://github.com/iTwin/presentation/pull/727): 1.0 release. | ||
| The APIs are now considered stable and ready for production use. | ||
| ### Patch Changes | ||
| - Updated dependencies: | ||
| - @itwin/presentation-shared@1.0.0 | ||
| ## 0.5.1 | ||
@@ -4,0 +17,0 @@ |
| { | ||
| "name": "@itwin/unified-selection", | ||
| "version": "0.5.1", | ||
| "version": "1.0.0", | ||
| "description": "Package for managing unified selection in iTwin.js applications.", | ||
@@ -34,3 +34,3 @@ "license": "MIT", | ||
| "rxjs-for-await": "^1.0.0", | ||
| "@itwin/presentation-shared": "^0.5.0" | ||
| "@itwin/presentation-shared": "^1.0.0" | ||
| }, | ||
@@ -70,4 +70,5 @@ "devDependencies": { | ||
| "extract-api": "extract-api --entry=unified-selection --apiReportFolder=./api --apiReportTempFolder=./api/temp --apiSummaryFolder=./api", | ||
| "check-internal": "node ../../scripts/checkInternal.js --apiSummary ./api/unified-selection.api.md" | ||
| "check-internal": "node ../../scripts/checkInternal.js --apiSummary ./api/unified-selection.api.md", | ||
| "validate-markdowns": "node ../../scripts/validateMarkdowns.js README.md" | ||
| } | ||
| } |
@@ -96,3 +96,3 @@ # @itwin/unified-selection | ||
| `@itwin/core-frontend` contains a concept called the [HiliteSet](https://www.itwinjs.org/reference/core-frontend/selectionset/hiliteset/). This concept is tightly related to unified selection, because, generally, we want selected elements to be highlighted in the application's graphics views. The `HiliteSet` object contains IDs of 3 types of elements: [GeometricModel](https://www.itwinjs.org/reference/core-backend/models/geometricmodel/), [SubCategory](https://www.itwinjs.org/reference/core-backend/categories/subcategory/) and [GeometricElement](https://www.itwinjs.org/reference/core-backend/elements/geometricelement/). On the other hand, the unified selection API allows selecting other kinds of elements too, so IDs of these elements need to be mapped to the supported ones. The rules are as follows: | ||
| `@itwin/core-frontend` contains a concept called the [HiliteSet](https://www.itwinjs.org/reference/core-frontend/selectionset/hiliteset/). This concept is tightly related to unified selection, because, generally, we want selected elements to be highlighted in the application's graphics views. The `HiliteSet` object contains IDs of 3 types of elements: [GeometricModel](https://www.itwinjs.org/reference/core-backend/models/geometricmodel/), [SubCategory](https://www.itwinjs.org/reference/core-backend/imodels/subcategory/) and [GeometricElement](https://www.itwinjs.org/reference/core-backend/elements/geometricelement/). On the other hand, the unified selection API allows selecting other kinds of elements too, so IDs of these elements need to be mapped to the supported ones. The rules are as follows: | ||
@@ -99,0 +99,0 @@ - for `BisCore.Subject` return IDs of all geometric models that are recursively under that Subject, |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.08%
416853
- Number of low quality alerts
- decreased by-50%
1
Dependency changes
+ Added@itwin/presentation-shared@1.1.0(transitive)
- Removed@itwin/presentation-shared@0.5.0(transitive)