Fetch a single Easee charger by id#42
Merged
Merged
Conversation
Resolving one charge point at a time only needs that charger's data
(notably its productCode), so expose GET /api/chargers/{id} instead of
forcing callers to page the whole account listing.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Voegt
Client#charger(id)toe: éénGET /api/chargers/{id}die eenChargerteruggeeft (incl.productCode), zodat callers voor het resolven van één laadpaal niet de hele account-lijst hoeven te pagineren.Nodig voor de charge-point-model-resolutie in StekkerWeb (stekker/stekker#8245): per lader één API-call i.p.v. de volledige lijst. De single-charger-response is op productie geverifieerd — die bevat
productCode(bevestigd met een echte Charge Pro:productCode: 103).