DriveSomethingGreater: log data point id before name

[andig]

The eu-data-act store's debug log printed only the map index per data point. This logs the point's unique GUID (id) before its delivered field name, so points are identifiable in traces (recv <id> <name>: <value> (<timestamp>)).

point now carries its Key (id) and Name; populated in points(), used in logData.

🤖 Generated with Claude Code

[sourcery-ai]

Hey - I've left some high level feedback:

• The point struct now duplicates the data field name both as the map key and as Name; consider whether you can rely on the existing map key instead of storing Name to avoid redundancy and potential divergence if they ever get out of sync.
• Given logData now uses p.Key and p.Name, it might be safer to explicitly document or enforce that points() is the only constructor for point, or add a small helper constructor, so these fields are always populated consistently.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `point` struct now duplicates the data field name both as the map key and as `Name`; consider whether you can rely on the existing map key instead of storing `Name` to avoid redundancy and potential divergence if they ever get out of sync.
- Given `logData` now uses `p.Key` and `p.Name`, it might be safer to explicitly document or enforce that `points()` is the only constructor for `point`, or add a small helper constructor, so these fields are always populated consistently.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}