Release packages [publish docs]

[imodeljs-admin]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@itwin/unified-selection@1.8.0

Minor Changes

• #1396: Expose CLEAR_SELECTION_STORAGE_SOURCE constant that is used as selection change event source when selection storage is cleared. This should allow consumers to detect when selection change happened due to selection storage being cleared.

  import {
    createStorage,
    CLEAR_SELECTION_STORAGE_SOURCE,
  } from "@itwin/unified-selection";
  
  const storage = createStorage();
  storage.selectionChangeEvent.addListener((args) => {
    if (args.source === CLEAR_SELECTION_STORAGE_SOURCE) {
      // ignore change if it was caused by clearing selection storage
    }
    // handle selection change
  });
  
  // this will trigger the `selectionChangeEvent` with `{ source: CLEAR_SELECTION_STORAGE_SOURCE }`
  storage.clearStorage({ imodelKey: imodel.key });

[github-actions]

Unified selection benchmark

Benchmark suite	Current: 762fc5e	Previous: 1c319fd	Deviation	Status
compute selection for 50k elements	374 ms	383 ms	-2.35%	〰️
compute selection for 50k elements (P95 of main thread blocks)	31 ms	32 ms	-3.13%	〰️
compute parent selection for 50k elements	345 ms	354 ms	-2.54%	〰️
compute parent selection for 50k elements (P95 of main thread blocks)	34 ms	31 ms	9.68%	〰️
compute top ancestor selection for 50k elements	570 ms	571 ms	-0.18%	〰️
compute top ancestor selection for 50k elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
compute category selection for 50k elements	107 ms	104 ms	2.88%	〰️
compute category selection for 50k elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
compute model selection for 50k elements	72 ms	82 ms	-12.20%	〰️
compute model selection for 50k elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
compute functional selection for 50k 3D elements	420 ms	432 ms	-2.78%	〰️
compute functional selection for 50k 3D elements (P95 of main thread blocks)	36 ms	35 ms	2.86%	〰️
compute parent functional selection for 50k 3D elements	442 ms	453 ms	-2.43%	〰️
compute parent functional selection for 50k 3D elements (P95 of main thread blocks)	34 ms	34 ms	0%	🟰
compute top ancestor functional selection for 50k 3D elements	1156 ms	1211 ms	-4.54%	〰️
compute top ancestor functional selection for 50k 3D elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
compute functional selection for 50k 2D elements	3070 ms	3187 ms	-3.67%	〰️
compute functional selection for 50k 2D elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
compute parent functional selection for 50k 2D elements	3121 ms	3158 ms	-1.17%	〰️
compute parent functional selection for 50k 2D elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
compute top ancestor functional selection for 50k 2D elements	3039 ms	3298 ms	-7.85%	〰️
compute top ancestor functional selection for 50k 2D elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
hilite 50k elements	1255 ms	1285 ms	-2.33%	〰️
hilite 50k elements (P95 of main thread blocks)	53 ms	55 ms	-3.64%	〰️
hilite 50k group elements	244 ms	243 ms	0.41%	〰️
hilite 50k group elements (P95 of main thread blocks)	31 ms	31 ms	0%	🟰
hilite 1k subjects	45516 ms	45764 ms	-0.54%	〰️
hilite 1k subjects (P95 of main thread blocks)	21 ms	29 ms	-27.59%	〰️
hilite 50k subcategories	297 ms	294 ms	1.02%	〰️
hilite 50k subcategories (P95 of main thread blocks)	40 ms	40 ms	0%	🟰
hilite 50k functional 3D elements	31776 ms	31262 ms	1.64%	〰️
hilite 50k functional 3D elements (P95 of main thread blocks)	42 ms	42 ms	0%	🟰
hilite 50k functional 2D elements	6857 ms	6944 ms	-1.25%	〰️
hilite 50k functional 2D elements (P95 of main thread blocks)	43 ms	39 ms	10.26%	〰️

This comment was automatically generated by workflow using github-action-benchmark.