@woosmap/react-native-plugin-geofencing 1.0.0-beta.1 → 1.0.0-beta.2

package/CHANGELOG.md

@@ -1,6 +1,5 @@
 ## 1.0.0
-- Enhancement: Introduced the `WoosmapGeofencingTurbo` TurboModule (New Architecture). 
-— The region-CRUD and key/radius methods  `addRegion`, `removeRegions`, `getRegions`, `setPoiRadius`, `setWoosmapApiKey` now dispatch through the generated codegen path. All other methods continue to flow through the legacy `PluginGeofencing` module. Public JS API is unchanged.
+- Enhancement: Introduced the `WoosmapGeofencingTurbo` TurboModule (New Architecture). The region-CRUD and key/radius methods — `addRegion`, `removeRegions`, `getRegions`, `setPoiRadius`, and `setWoosmapApiKey` — now dispatch through the generated codegen path. All other methods continue to flow through the legacy `PluginGeofencing` module. The public JS API is unchanged.
 
 ## 0.14.0
 - Breaking: Raised minimum supported React Native to `0.85.x`; React `19.2.3`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@woosmap/react-native-plugin-geofencing",
-  "version": "1.0.0-beta.1",
+  "version": "1.0.0-beta.2",
   "description": "This react-native plugin extends the functionality offered by the Woosmap Geofencing Mobile SDKs. Find more about the Woosmap Geofencing SDK",
   "main": "lib/commonjs/index",
   "module": "lib/module/index",
@@ -8,6 +8,7 @@
   "source": "src/index",
   "files": [
     "lib",
+    "src/NativeWoosmapGeofencingTurbo.ts",
     "android",
     "ios",
     "cpp",

package/src/NativeWoosmapGeofencingTurbo.ts

@@ -0,0 +1,56 @@
+import type { TurboModule } from 'react-native';
+import { TurboModuleRegistry } from 'react-native';
+
+/**
+ * Geofence region payload accepted by {@link Spec.addRegion}.
+ *
+ * Codegen supports a narrower subset of TypeScript than the public
+ * `GeofenceRegion` interface in `internal/types`. String-literal unions
+ * (`'circle' | 'isochrone'`) are not expressible in a spec, so `type` is
+ * widened to `string` here. The JS facade keeps the strict union for
+ * consumers — the widening is internal to the native boundary only.
+ */
+export type GeofenceRegionInput = {
+  regionId: string;
+  lat: number;
+  lng: number;
+  radius: number;
+  type: string;
+};
+
+/**
+ * Region record returned by {@link Spec.getRegions}. Mirrors the native
+ * payload shape (lower-cased keys) before the facade maps it onto the
+ * `Region` class via `Region.jsonToObj`.
+ */
+export type RegionRecord = {
+  date: number;
+  didenter: boolean;
+  identifier: string;
+  latitude: number;
+  longitude: number;
+  radius: number;
+  frompositiondetection: boolean;
+  eventname: string;
+  spenttime: number;
+};
+
+/**
+ * TurboModule spec for the region-CRUD + key/radius slice migrated in
+ * Event emitters, background lifecycle and the
+ * remaining ~27 methods stay on the legacy `PluginGeofencing` module.
+ *
+ * The codegen module name is `WoosmapGeofencingTurbo`; the generated spec
+ * artifacts are named `WoosmapGeofencingTurboSpec` (see `codegenConfig` in
+ * package.json).
+ */
+export interface Spec extends TurboModule {
+  addRegion(region: GeofenceRegionInput): Promise<string>;
+  removeRegion(regionId: string): Promise<string>;
+  removeAllRegions(): Promise<string>;
+  getRegions(regionId?: string): Promise<RegionRecord[]>;
+  setPoiRadius(radius: string): Promise<string>;
+  setWoosmapApiKey(apiKey: string): Promise<string>;
+}
+
+export default TurboModuleRegistry.getEnforcing<Spec>('WoosmapGeofencingTurbo');