-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
Push Overseerr updates via webhook #134187
base: dev
Are you sure you want to change the base?
Conversation
| NotificationType.REQUEST_PROCESSING_FAILED | ||
| NotificationType.REQUEST_AUTOMATICALLY_APPROVED | ||
) | ||
JSON_PAYLOAD = ( |
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.
how HA specific is this/could this be generated in the lib based on notification types as input (tbh I don't really love having this here)
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.
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 get that, I was thinking about moving that shaping part to the lib, just so we don’t handle raw json here. Can we at least prettify the formatting (triple string) if it stays here for readability?
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.
The fun part is that I removed all space in between, as apparently overseerr seems to mess with spaces.
But I think moving the shape to the library leaves you still with a mess because how are you going to shape parameters for that
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.
was thinking about passing lists per top level key since it's always key: {{key}}
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.
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.
exactly, that's why I said per top level key as those are different
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.
But someone can wish to have a different layout and not have these keys there
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 get that, was just looking for a way to avoid a large raw json block here
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Proposed change
Push Overseerr updates via webhook. We try to setup the webhook during setup of the integration.
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: