-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Planner: drop deprecated publishing keys #2 (BC) #26540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
@naltatis had no write access |
| Time time.Time `json:"time"` | ||
| Soc int `json:"soc"` | ||
| Time time.Time `json:"time"` | ||
| PlanStrategy api.PlanStrategy `json:"planStrategy"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PlanStrategy has effect for the static Plan and for RepeatingPlans. Therefore I wouldn't nest into the static plan and keep it directly in vehicleStruct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andig this was your refactoring, wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andig friendly ping ;-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like this as part of the plan- a strategy always relates to a (repeating) plan. But looking at https://github.com/evcc-io/evcc/pull/26540/changes#diff-65aed087489435cf1207d29104c2436829844af8ada75323d641e2b4bdc17058R19, we also need to do this for the repeating plan.
Co-authored-by: Michael Geers <michael@geers.tv>
Follow-up to #24423, depends on #26291
based on #26293
TODO: