@itwin/unified-selection 0.5.1 → 1.0.0

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @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
 
 ### Patch Changes

package/README.md

@@ -93,7 +93,7 @@ With that in mind, the above components _A_, _B_ and _C_ can be configured as fo
 
 > **Note:** hilite = highlight
 
-`@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:
 
 - for `BisCore.Subject` return IDs of all geometric models that are recursively under that Subject,
 - for `BisCore.Model` just return its ID,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@itwin/unified-selection",
-  "version": "0.5.1",
+  "version": "1.0.0",
   "description": "Package for managing unified selection in iTwin.js applications.",
   "license": "MIT",
   "repository": {
@@ -31,7 +31,7 @@
     "@itwin/core-bentley": "^4.9.0",
     "rxjs": "^7.8.1",
     "rxjs-for-await": "^1.0.0",
-    "@itwin/presentation-shared": "^0.5.0"
+    "@itwin/presentation-shared": "^1.0.0"
   },
   "devDependencies": {
     "@itwin/build-tools": "^4.9.0",
@@ -66,6 +66,7 @@
     "test": "mocha --enable-source-maps --config ./.mocharc.json \"./lib/cjs/test/**/*.test.js\"",
     "test:watch": "npm -s test -- --reporter min --watch-extensions ts --watch",
     "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"
   }
 }