mgtypes 1.0.98 → 1.0.99

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mgtypes",
3
- "version": "1.0.98",
3
+ "version": "1.0.99",
4
4
  "description": "types for mg development",
5
5
  "main": "index.js",
6
6
  "scripts": {
@@ -40,13 +40,10 @@ export enum mgNotificationsPermissionTitle {
40
40
  }
41
41
 
42
42
  // STATE //////////////////////////////////////////////
43
+ // THESE ARE ALL THE PERMISSIONS THAT MOBGOB HAS AT WRITING
43
44
  export interface mgPermissionsState {
44
- NATIVE: {
45
- [permission: string]: mgNativePermission;
46
- };
47
- LOCATION: {
48
- [permission: string]: mgNonNativePermission;
49
- };
45
+ SHOW_LOCATION_AND_DISTANCES: mgNonNativePermission;
46
+ LOCATION_FOREGROUND: mgNativePermission;
50
47
  }
51
48
 
52
49
  export interface mgNativePermission {
@@ -412,9 +412,13 @@ export interface mgPermissionsProfile {
412
412
  };
413
413
  // ARE THESE PERMISSIONS NEEDED FOR THE USER'S
414
414
  // VERSION OF THE APP? IF SO, THEY APPEAR IN SETTINGS
415
+ // 'isRequired' here refers to whether the configuration of the
416
+ // app has features that require that permission. So the Location_foreground
417
+ // is required if the app is configured to allow SHOW_LOCATION_AND_DISTANCES.
418
+ // The other native permissions are commented out because
419
+ // there are no finished features in the app that require them.
415
420
  NATIVE_PERMISSIONS: {
416
421
  LOCATION_FOREGROUND: { isRequired: boolean; requestOnInit: boolean };
417
- // TODO:permissionsConfig
418
422
  // LOCATION_BACKGROUND: { isRequired: boolean; requestOnInit: boolean };
419
423
  // MEDIA_LIBRARY: { isRequired: boolean; requestOnInit: boolean };
420
424
  // REMINDERS: { isRequired: boolean; requestOnInit: boolean };