bckelley/cgm-remote-monitor
1
0
Fork 0
mirror of https://github.com/bckelley/cgm-remote-monitor.git synced 2026-08-24 03:14:12 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs: use neutral wording for UUID handling description

Browse Source 
Avoid implying all AID clients use the same pattern or that any
specific implementation is incorrect. Different clients have
divergent sync patterns - the feature accommodates this variety.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Ben West
2026-03-17 14:32:05 -07:00
co-authored by Copilot
parent abb505b256
commit a2c6ce1e5a
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -252,7 +252,7 @@ To learn more about the Nightscout API, visit https://YOUR-SITE.com/api-docs/ or
Setting it to `denied` will require a token from every visit, using `status-only` will enable api-secret based login.
* `IMPORT_CONFIG` - Used to import settings and extended settings from a url such as a gist. Structure of file should be something like: `{"settings": {"theme": "colors"}, "extendedSettings": {"upbat": {"enableAlerts": true}}}`
* `TREATMENTS_AUTH` (`on`) - possible values `on` or `off`. Deprecated, if set to `off` the `careportal` role will be added to `AUTH_DEFAULT_ROLES`
* `UUID_HANDLING` (`true`) - Controls how UUID `_id` values are handled for treatments and entries. When `true` (default), UUID values in `_id` are extracted to an `identifier` field and the server generates a proper ObjectId. This enables sync with Loop, Trio, AAPS, and xDrip+ which use UUID patterns. Set to `false` for strict mode where UUID `_id` values are rejected.
* `UUID_HANDLING` (`true`) - Controls how UUID `_id` values are handled for treatments and entries. When `true` (default), UUID values in `_id` are extracted to an `identifier` field and the server generates a proper ObjectId. This accommodates various client sync patterns that may include UUID identifiers. Set to `false` for strict mode where UUID `_id` values are rejected.
#### Data Rights
docs/example-template.env
+2 -2
View File
@@ -14,12 +14,12 @@ PORT=1337
NODE_ENV=development
AUTH_FAIL_DELAY=50
# UUID handling for AID clients (Loop, Trio, AAPS, xDrip+)
# UUID handling for various AID client sync patterns
# When true (default): UUID _id values are normalized to 'identifier' field
# - POST/PUT: UUID in _id extracted to identifier, server generates ObjectId
# - GET/DELETE: UUID _id searches by identifier field
# When false: Strict mode - UUID _id values rejected on write, ignored on read
# Default is true to support Loop, Trio, AAPS, xDrip+ UUID sync patterns
# Default is true to accommodate clients that may include UUID identifiers
# UUID_HANDLING=true
#
# Set to false for strict ObjectId-only mode:
lib/server/env.js
+1 -1
View File
@@ -76,7 +76,7 @@ function setSSL () {
env.secureCsp = readENVTruthy("SECURE_CSP", false);
env.secureCspReportOnly = readENVTruthy("SECURE_CSP_REPORT_ONLY", false);
// UUID handling for AID clients (Loop, Trio, AAPS, xDrip+)
// UUID handling for various AID client sync patterns
// When true (default): UUID _id values are normalized to 'identifier' field
// When false: UUID _id values are rejected on write, ignored on read (strict mode)
env.uuidHandling = readENVTruthy("UUID_HANDLING", true);