Support for Custom Configuration Keys for OCPP1.6 #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pietfried
force-pushed
the
pg-custom-config-keys-16
branch
2 times, most recently
from
6a5ba32 to
1c71c6f
Compare
hikinggrass
approved these changes
Sep 18, 2023
Pietfried
force-pushed
the
pg-custom-config-keys-16
branch
from
dacba1f to
b8f4c35
Compare
* the option to register callbacks for specific keys that are executed when those keys change initiated by CSMS * an API call to retrieve configuration parameters * an API call to set custom configuration key in case they have changed internally removed contents from Custom.json json schema Signed-off-by: pietfried <[email protected]>
Pietfried
force-pushed
the
pg-custom-config-keys-16
branch
from
b8f4c35 to
09b1374
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added support for custom configuration keys for 1.6. This includes: