Bump version to 1.0.9 and document known limitations for private airp…#10
Merged
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
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.
This pull request updates the integration to version 1.0.9, adds documentation about known limitations with private airports, and improves test coverage for flight type filtering in the sensor entity.
Documentation updates:
README.mdto document that the integration does not supplement missing data for private airports (e.g., TRF/Torp), and that such airports may have incomplete or missing data due to upstream limitations. [1] [2]README.mdto mention the new documentation about private airport limitations.Version bump:
1.0.9in both theREADME.mdbadge andmanifest.json. [1] [2]Test improvements:
tests/test_api_parsing.pyto verify thatAvinorFlightsSensorapplies the flight type filter correctly per sensor entity. [1] [2]…orts