Skip to content

Conversation

@heindrichpaul
Copy link
Contributor

Breaking change

NO

Proposed change

This adds diagnostics support to the Nederlandse spoorwegen integration.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @YarmoM, mind taking a look at this pull request as it has been labeled with an integration (nederlandse_spoorwegen) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nederlandse_spoorwegen can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign nederlandse_spoorwegen Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds diagnostics support to the Nederlandse Spoorwegen integration, enabling users to extract debugging information at both the config entry and device levels. The implementation collects coordinator data, route information, and trip details while properly redacting sensitive API keys.

Key Changes

  • Added diagnostics.py module with config entry and device-level diagnostics functions
  • Created comprehensive test coverage with snapshot assertions
  • Implemented proper data redaction for API keys

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
homeassistant/components/nederlandse_spoorwegen/diagnostics.py Implements diagnostics data collection for config entries and devices, including coordinator info, route data, and trip details with API key redaction
tests/components/nederlandse_spoorwegen/test_diagnostics.py Adds test coverage for both entry and device diagnostics with snapshot assertions
tests/components/nederlandse_spoorwegen/snapshots/test_diagnostics.ambr Defines expected diagnostic output snapshots for verification
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment