isard 2.4.0 → 2.4.1
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 +17 -0
- package/dist/isard_grid_bg.wasm +0 -0
- package/dist/isard_webgl2_bg.wasm +0 -0
- package/dist/isard_webgpu_bg.wasm +0 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,23 @@ versions [Semantic Versioning](https://semver.org) (before 1.0.0, a minor versio
|
|
|
5
5
|
|
|
6
6
|
## [Unreleased]
|
|
7
7
|
|
|
8
|
+
## [2.4.1] - 2026-11-02
|
|
9
|
+
|
|
10
|
+
With `isard-react-native` and `isard-map` (Python) 2.4.1.
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- `<IsardMapView>`'s `onReady` gets the view's handle, the object its ref gives (`onReady={(view) => …}`): what the app
|
|
15
|
+
adds once by isard's API, or reads in the page, goes there in place of an effect, called again if the page loads
|
|
16
|
+
again. A callback without an argument goes on working. React Native's examples write no `useEffect` any more: their
|
|
17
|
+
layers added in `onReady`, the map changed where the app's state changes, the phone's position watched by a hook of
|
|
18
|
+
their own (`useLocation`)
|
|
19
|
+
|
|
20
|
+
### Fixed
|
|
21
|
+
|
|
22
|
+
- The documentation site built again: the React page *Loading data* had double braces in its text, read by VitePress
|
|
23
|
+
as an expression
|
|
24
|
+
|
|
8
25
|
## [2.4.0] - 2026-11-01
|
|
9
26
|
|
|
10
27
|
With `isard-react-native` and `isard-map` (Python) 2.4.0.
|
package/dist/isard_grid_bg.wasm
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
package/package.json
CHANGED