Fix: Subsequent validation of existing profiles for OCPP2.0.1 #837
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
Fixed validation of TxProfile(s) by checking profile id so profiles are the same profiles do not conflict Fixed check for overlapping validity period. The chargingProfileKind was used although K01.FR.06 requires chargingProfilePurpose instead Signed-off-by: Piet Gömpel <[email protected]>
Pietfried
requested review from
hikinggrass,
marcemmers and
maaikez
as code owners
4 tasks
hikinggrass
approved these changes
Oct 16, 2024
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
The combination that was checked before this change was:
stackLevel - chargingProfileKind- evseId
These changes allow OCTT TC_K_41_CS to PASS.
Issue ticket number and link
#819
Checklist before requesting a review