Loadpoint: fix updating charger soc

[andig]

Fix #20749

[sourcery-ai]

Hey - I've left some high level feedback:

• In TestPublishSocAndRangeVehiclesAndChargers, consider using t.Run(tc.name, func(t *testing.T) { ... }) instead of a plain loop plus t.Log, so that each case runs as a named subtest and is easier to target and debug.
• For offlineVehicle.EXPECT().Soc().AnyTimes() and similar expectations without explicit .Return(...), you are relying on gomock's zero-value defaults; if the behavior matters, it would be clearer and safer to specify the return values explicitly to avoid accidental reliance on mock defaults.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `TestPublishSocAndRangeVehiclesAndChargers`, consider using `t.Run(tc.name, func(t *testing.T) { ... })` instead of a plain loop plus `t.Log`, so that each case runs as a named subtest and is easier to target and debug.
- For `offlineVehicle.EXPECT().Soc().AnyTimes()` and similar expectations without explicit `.Return(...)`, you are relying on gomock's zero-value defaults; if the behavior matters, it would be clearer and safer to specify the return values explicitly to avoid accidental reliance on mock defaults.

---

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.}