feat(OCPP201): add variable mapping support between OCPP201 Device Model and EVerest config #1571
Conversation
This file contains hidden or 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
…del and EVerest config * Introduce VariableMapping class with YAML-based mapping & JSON schema validation * Add mapping.yaml & mapping_schema.json for configurable mappings * Extend EverestDeviceModelStorage to apply bidirectional mappings * Update ComposedDeviceModelStorage to merge and validate mapped variables * Add MappingFilePath config option in manifest * Enhance documentation with mapping strategy and updated device model architecture Signed-off-by: Piet Gömpel <[email protected]>
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.
Describe your changes
Issue ticket number and link
Original PR: #1259
Checklist before requesting a review