feat: v1.8.0 release - #83
Merged
Merged
Conversation
Adds optional language parameter to the add_parcel service, allowing users to specify the language for delivery information (ISO 639-1 two-letter code). This addresses issue #70 and aligns with the Parcel App API which supports an optional 'language' parameter for the add-delivery endpoint. Changes: - Added LANGUAGE and DEFAULT_LANGUAGE constants to const.py - Updated ADD_PARCEL_SCHEMA to include optional language field - Modified async_add_parcel to include language in API payload - Added language field to services.yaml - Added translation strings for language field Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Adds three new attributes to the ActiveShipment sensor to expose delivery window information when provided by carriers: - date_expected_end: End of delivery window (for carriers that provide time ranges) - timestamp_expected: Epoch timestamp for expected delivery (more precise, includes timezone) - timestamp_expected_end: End of delivery window as epoch timestamp These attributes are already parsed from the API response and stored in the Shipment class but were not previously exposed to Home Assistant. This enables users to create more precise automations based on delivery windows. Also updates EMPTY_ATTRIBUTES in const.py for consistency. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Update test assertions to include date_expected_end, timestamp_expected, and timestamp_expected_end attributes that were added to EMPTY_ATTRIBUTES. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Move language field before send_push_confirmation for better UX as requested in PR review. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Per maintainer feedback: - Added date_expected_end, timestamp_expected, timestamp_expected_end attributes to RecentShipment sensor (matching ActiveShipment) - Updated recent.json fixture with actual delivery window values - Updated tests to verify non-None delivery window values - Added dedicated test_delivery_window_attributes test - Fixed TypeError handling for timestamp parsing (caught by CodeRabbit) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…acking_number_data patterns
…12 compatibility for description_placeholders
…dow-attributes' into release/v1.8.0-beta # Conflicts: # tests/test_sensors.py
…ter' into release/v1.8.0-beta # Conflicts: # custom_components/parcelapp/translations/en.json
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
2 participants
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.
Summary
courierfield is now optional; carriers are auto-detected from tracking numbers using regex patterns and checksum validation from jkeen/tracking_number_datadate_expected_end,timestamp_expected, andtimestamp_expected_endon sensorslanguagefield onadd_parcelservice for localized delivery infoBeta tested as
v1.8.0-beta.1.Closes #72, closes #73, closes #80