@procore/bim-webviewer-sdk 2.0.0 → 2.1.0-BIM-1749-rc1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -5,11 +5,41 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
|
|
7
7
|
|
|
8
|
+
## [Unreleased]
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- BREAKING CHANGE - Static method Cache.removeModel use to return false if a model could not be removed from cache. It will now throw an error.
|
|
13
|
+
- NOT GENERALLY AVAILABLE - Gated by the 'bim-webviewer-effect-composition' LanchDarkly switch. Uses the EffectComposer rendering pipeline to generate the 3D views. This is released as an experiment to understand the impact on staging and production.
|
|
14
|
+
- Refactored Node into a true primitive, implementing lazy evaluation of its attributes.
|
|
15
|
+
|
|
16
|
+
### Added
|
|
17
|
+
|
|
18
|
+
- Added mechanism to only cache the most recently viewed version of a model when the model was loaded with a `fileExtractionId`.
|
|
19
|
+
- This behavior already existed for models loaded with a `modelId` and `modelRevisionId`.
|
|
20
|
+
- `Cache.removeModel(options)` now removes models loaded with a `fileExtractionId` when `options` contains that `fileExtractionId`.
|
|
21
|
+
- This behavior already existed for models loaded with a `modelId` and `modelRevisionId` when `options` contains `modelId`.
|
|
22
|
+
|
|
23
|
+
## [2.1.0] - 2022-04-18
|
|
24
|
+
|
|
25
|
+
### Changed
|
|
26
|
+
|
|
27
|
+
- Improve accuracy of transparency once at rest
|
|
28
|
+
|
|
29
|
+
### Added
|
|
30
|
+
|
|
31
|
+
- Added loading states out of the box. These can be enabled by adding the `LOADING` tool to the `tools` array when initializing the Webviewer. For example: `tools: [Webviewer.tools.LOADING]`.
|
|
32
|
+
|
|
33
|
+
### Fixed
|
|
34
|
+
|
|
35
|
+
- Fixed CSS issue in Model Objects tree window involving alignment of the show/hide toggles.
|
|
36
|
+
|
|
8
37
|
## [2.0.0] - 2022-03-25
|
|
9
38
|
|
|
10
39
|
### Added
|
|
11
40
|
|
|
12
41
|
- Caching is now handled internally by the Webviewer SDK. Prior to this release, the only way we allowed for cached models was through a Service Worker provided separately from this npm package (or implementing one yourself). If you were using a service worker in this way, it will no longer be registered by the SDK and from the SDK's perspective is useless and can be deleted.
|
|
42
|
+
|
|
13
43
|
### Changed
|
|
14
44
|
|
|
15
45
|
- [BREAKING CHANGE] Change `enableWebWorker` option default to true. If you were not declaring this option before and want to maintain the old behavior then you must set `enableWebWorker: false`. We will still check if Web Workers are supported by the environment even if this is unset or set to true and gracefully fallback if they are not supported.
|