@itwin/unified-selection
Advanced tools
Comparing version 1.1.1 to 1.1.2
# @itwin/unified-selection | ||
## 1.1.2 | ||
### Patch Changes | ||
- Updated dependencies: | ||
- @itwin/presentation-shared@1.2.0 | ||
## 1.1.1 | ||
@@ -4,0 +11,0 @@ |
{ | ||
"name": "@itwin/unified-selection", | ||
"version": "1.1.1", | ||
"version": "1.1.2", | ||
"description": "Package for managing unified selection in iTwin.js applications.", | ||
@@ -39,9 +39,9 @@ "license": "MIT", | ||
"dependencies": { | ||
"@itwin/core-bentley": "^4.9.0", | ||
"@itwin/core-bentley": "^4.10.1", | ||
"rxjs": "^7.8.1", | ||
"rxjs-for-await": "^1.0.0", | ||
"@itwin/presentation-shared": "^1.1.0" | ||
"@itwin/presentation-shared": "^1.2.0" | ||
}, | ||
"devDependencies": { | ||
"@itwin/build-tools": "^4.10.0-dev.33", | ||
"@itwin/build-tools": "^4.10.1", | ||
"@itwin/eslint-plugin": "5.0.0-dev.1", | ||
@@ -65,4 +65,4 @@ "@types/chai": "^4.3.16", | ||
"typescript": "~5.6.3", | ||
"presentation-test-utilities": "^0.0.0", | ||
"presentation-build-tools": "^0.0.0" | ||
"presentation-build-tools": "^0.0.0", | ||
"presentation-test-utilities": "^0.0.0" | ||
}, | ||
@@ -69,0 +69,0 @@ "scripts": { |
@@ -135,3 +135,3 @@ # @itwin/unified-selection | ||
#### Selection scopes | ||
### Selection scopes | ||
@@ -138,0 +138,0 @@ Selection scopes allow decoupling of what gets picked and what gets selected. Without selection scopes, whenever a user picks an element in the viewport, its ID goes straight into unified selection storage. With selection scopes we can modify that and add something different. The input to the selection scopes' processor is a query executor, element IDs, and the scope to apply, and the output is an iterator of `SelectableInstanceKey`. We get the input when the user picks some elements in the viewport, run that through the selection scope processor and put the output into unified selection storage. |
421857