[2.8] Linked identity history in detail, history and M2M APIs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
The work touches the serializers that should expose previous_identities and successor, the node detail, telemetry/position history and M2M endpoints, and the M2M OpenAPI spec. Read the blocking issue pskillen/meshflow-api#440 (ID-2) first, since this depends on it. Done means charts span an identity upgrade without a gap, the endpoints run without N+1 queries, and the OpenAPI spec is updated.
Written by the indexing model from the issue text.
Description
Part of pskillen/meshflow-api#437 (Meshtastic 2.8.x support). Code: ID-6 · Priority: Should · Size: L
Summary
Read-through history across linked identities: node detail, telemetry/position history, M2M endpoints. Expose previous_identities / successor in serializers and update the M2M OpenAPI spec.
Acceptance criteria
- Charts span an upgrade without a gap
- No N+1 queries
- OpenAPI updated
Depends on: pskillen/meshflow-api#440 (ID-2)
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pskillen/meshflow-api
-
enhancement meshtastic-2.8
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pskillen/meshflow-api#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 73/100
pskillen/meshflow-api#472 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 22/100
pskillen/meshflow-api#464 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pskillen/meshflow-api#463 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pskillen/meshflow-api#462 ·
Maintainers usually reply within 1 day
All issues in pskillen/meshflow-api
Similar issues
-
Paraxial.trace returns NaN for an object at infinity when the entrance pupil is at the first surfaceOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement ios launcher
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Substrait consumer doesn't recognise `shift_left` / `shift_right` from functions_arithmetic.yamlOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/datafusion#27059 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
loteran/Arctis-Sound-Manager#368 ·
Maintainers usually reply within 1 day
-
feed submission
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MobilityData/mobility-database-catalogs#1787 ·
Maintainers usually reply within 2 days