Browse Source

docs: update readmes to reflect dedicated MeshCore SWG schemas (PR #2784)

Both plugin readmes listed the SWGMeshtastic* placeholder as an
outstanding item needing dedicated SWGMeshcore* schemas. This PR
provides exactly that — strike the stale todo and note the resolution.
chirpmodem-v8.0.0
Tom Hensel 5 months ago
parent
commit
dd0b2a4f1d
No known key found for this signature in database
  1. 6
      plugins/channelrx/demodmeshcore/readme.md
  2. 6
      plugins/channeltx/modmeshcore/readme.md

6
plugins/channelrx/demodmeshcore/readme.md

@ -42,10 +42,8 @@ Functional surfaces: @@ -42,10 +42,8 @@ Functional surfaces:
keys dialog rather than a numbered Channel selector.
Outstanding:
- WebAPI schema reuses `SWGMeshtasticDemodSettings` /
`SWGMeshtasticDemodReport` as a placeholder; a dedicated
`SWGMeshcoreDemod*` schema would require regenerating the SWG
bindings.
- WebAPI schema now uses dedicated `SWGMeshcoreDemodSettings` /
`SWGMeshcoreDemodReport` schemas (no longer a placeholder).
<h2>References</h2>

6
plugins/channeltx/modmeshcore/readme.md

@ -49,9 +49,9 @@ Functional surfaces: @@ -49,9 +49,9 @@ Functional surfaces:
concept.
Outstanding:
- WebAPI schema reuses `SWGMeshtasticModSettings` as a placeholder; a
dedicated `SWGMeshcoreMod*` schema would require regenerating the
SWG bindings.
- WebAPI schema now uses dedicated `SWGMeshcoreModSettings` /
`SWGMeshcoreModReport` / `SWGMeshcoreModActions` schemas (no longer
a placeholder).
<h2>MESHCORE: command syntax</h2>

Loading…
Cancel
Save