zjs81/meshcore-open
1
0
Fork 0
mirror of https://github.com/zjs81/meshcore-open.git synced 2026-07-12 11:52:07 +10:00
Code Issues Packages Projects Releases 2 Wiki Activity

fix case-sensitive prefix

Browse Source
This commit is contained in:
PacoX
2026-05-26 09:04:38 +02:00
parent 3a11e35a7a
commit e88281b7b6
4 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/routing-paths.md
+1
View File
@@ -37,6 +37,7 @@ The connector reads a single-mode byte and clamps to `0..3`, so the supported ho
Paths in messages and storage consist of:
- **`pathLength`**: Encoded path length in bytes as carried by the frame/header. This is not the hop count when `pathHashByteWidth > 1`.
- Note: on-air headers carry `pathLength` as a byte count. However, in the app's data model and storage the `pathLength` field is stored as the decoded hop count (number of hops). When reading or writing model objects (contacts, messages, storage), treat `pathLength` as the hop count; when constructing frames use the encoded byte length.
- **`pathBytes`**: Raw bytes of the path, grouped by `pathHashByteWidth`
- **`hopCount`**: Derived display value computed from bytes and width: `(byteCount + hashByteWidth - 1) ~/ hashByteWidth`
- **Example**: With `pathHashByteWidth=2`, a 3-hop path needs 6 bytes, so `pathLength = 6` and `hopCount = 3`: