Skip to content

Chore: update docstring - #240

Open
fhaver-amsterdam wants to merge 1 commit into
mainfrom
chore/update-docstring
Open

Chore: update docstring#240
fhaver-amsterdam wants to merge 1 commit into
mainfrom
chore/update-docstring

Conversation

@fhaver-amsterdam

Copy link
Copy Markdown
Contributor

Changes

Logic in the function was already like the new logic described in docstrings (and tests are in place to verify this).

Affected services

  • bridge

Definition of done

  • API is backwards compatible (make openapi-diff)
    - [ ] Swagger UI up-to-date & tested (make dev)
    - [ ] Dependencies updated (make requirements)
    - [ ] Infrastructure config updated (aapp_azure_infra)
    - [ ] Loadtests for relevant endpoints (aapp_testing_loadtests)

After PR created (and deployed on dev):

  • Manual check on dev (o) e.g. use feature via Swagger or admin panel
  • Sanity check on test app (check that dev environment is selected)

Other notes

GitHub Copilot was used in writing the code

@fhaver-amsterdam
fhaver-amsterdam requested review from a team and a lite review from Copilot August 28, 2026 08:17

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates internal documentation in the bridge service to better describe how a boat-charging location’s overall status and max kW are derived from socket data.

Changes:

  • Refines the _get_status_and_kw_from_sockets docstring to describe location-level status semantics.
  • Renames a local variable from available to operative for clearer intent when computing max kW.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +108 to 112
There are three possible status values for a location:
- "OPERATIVE": at least one connector at the location is operative
- "OCCUPIED": all connectors at the location are occupied
- "INOPERATIVE": no connector is operative and at least one connector is out of order
- "OCCUPIED": no connector is operative and at least one connector is occupied
- "INOPERATIVE": all connectors are out of order

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants