-
-
Notifications
You must be signed in to change notification settings - Fork 34.4k
Signal messenger flexible recipients #145654
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
base: dev
Are you sure you want to change the base?
Signal messenger flexible recipients #145654
Conversation
This enables the user to overwrite the default recipient list (which is configured globally) on a per-message basis by using the `target` attribute inherited from `notify`.
This enables the user to overwrite the default recipient list (which is configured globally) on a per-message basis by using the `target` attribute inherited from `notify`.
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.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Hey there @bbernhard, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
Thanks for the improvements! Looks good to me! |
Hi @bbernhard, thanks for having a look! As a first-time contributor, I have a question: how is the PR able to progress further? Can you approve it? Or do I need more patience, and in some days someone with write access will approve it once he/she sees that you agreed to the changes? |
Just approved your changes. But I guess a core maintainer might need to approve your PR too. My last contribution is already a while ago, so unfortunately I can't remember anymore how it exactly worked - sorry! |
Proposed change
Up to now, the signal_messenger integration was configured with a fixed list of recipients which could not be changed later. The consequence is that you have to configure the integration n times if you want to send messages to n people or groups.
This change enables the user to optionally overwrite the integration's global recipient list on a per-message basis by using the
target
attribute inherited fromnotify
. The recipient list still has to be configured globally for the integration, at least as a default.Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
.To help with the load of incoming pull requests: