🪠 Plumb through notify_charging_limit as a NOP #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So that we can finish testing the EVerest changes in EVerest/everest-demo#101 end-to-end
I have not yet plumbed through the changes to
clear_charging_limit
but they should be fairly simple, and I can leave them as an exercise for @Abby-WheelisOutline of changes:
notify_charging_limit
to theCallMap
, and have it redirect to thenotify_charging_limit_handler
notify_charging_limit
Testing done:
Without this change:
EVerest/everest-demo#101 (comment)
With this change: