-
-
Notifications
You must be signed in to change notification settings - Fork 37.8k
Support multiple attachments in signal messenger integration #31141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
rohankapoorcom
merged 12 commits into
home-assistant:dev
from
bbernhard:signalmessenger_multiple_attachments
Feb 1, 2020
Merged
Changes from 2 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
e709d24
added support for multiple attachments to signal_messenger integration
5463b25
updated pysignalclirestapi version in requirements_all.txt
0a15af1
reworked multiple attachments feature in signal_messenger integration
a181e14
reworked multiple attachments feature in signal_messenger integration
79d321c
small change in signal_messenger integration
236dc56
small changes in signal_messenger integration
1d22862
Merge branch 'dev' into signalmessenger_multiple_attachments
74bdee6
re-generated requirements_test_pre_commit.txt
067a3b6
added tests for signal_messenger integration
e4430d6
regenerated requirements_test_all.txt for signal_messenger integration
816886c
added more signal_messenger tests
bfab393
remove signal_messenger integration files from .coveragerc
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer that we avoid the breaking change unnecessarily here.
This could be done by allowing both the attribute
filenameas well as the attributefilenamesto be provided and then internally adding thefilenameto the list offilenames.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me 👍 I'll adapt the PR, thanks!
Should the
attachmentoption also be mentioned in the documentation then, or would you see that primarily as a way to stay backwards compatible and as something that's not worth mentioning in the documentation?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would mark it as deprecated and log a warning that it's deprecated and will be removed in version x.y.z (pick a version that's like 3 versions out).
If you are using vol to validate the schema of the service call, we have the deprecated validation helper in
config_validationAlternatively we could keep using attachment as the key and accept both a singular string or a list of strings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for your suggestions, very much appreciated!
I've updated the PR, please let me know if there's anything else that needs to be changed.
(I've also removed the
Breaking changessection from the PR description)