Skip to content
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

fix: fix deprecated hass.components use #2468

Merged

Conversation

danielbrunt57
Copy link
Collaborator

@danielbrunt57 danielbrunt57 commented Aug 18, 2024

replace hass.components.persistent_notification.async_dismiss with async_diismiss_persistent_notification
addresses deprecated warning in issue in #2467

replace hass.components.persistent_notification.async_dismiss with async_diismiss_persistent_notification
@alandtse
Copy link
Owner

Does this require a min HA bump?

@danielbrunt57
Copy link
Collaborator Author

Does this require a min HA bump?

That is a good question...

@danielbrunt57
Copy link
Collaborator Author

danielbrunt57 commented Aug 20, 2024

Does this require a min HA bump?

No. homeassistant 2024.2.0b0 components.persistent_notification contains async_create() and async_dismiss().

So why was this question not raised on PR #2400 for the same changes in __init__.py and config_flow.py?

@alandtse
Copy link
Owner

Sometimes I forget.

@alandtse alandtse changed the title fix: replace deprecated hass.components usage in config_flow.py fix: fix deprecated hass.components use Aug 20, 2024
@alandtse alandtse merged commit d5377e4 into alandtse:dev Aug 20, 2024
3 checks passed
alandtse added a commit that referenced this pull request Aug 20, 2024
fix: fix deprecated hass.components use (#2468)
@alandtse
Copy link
Owner

alandtse commented Aug 20, 2024

Oh also, if you're talking about what was reverted in #2396. You also just merged without waiting for approval. That's a bit hard for me to ask the question when you don't wait.

@danielbrunt57
Copy link
Collaborator Author

danielbrunt57 commented Aug 20, 2024

Ok, my mistake. You authored #2400 to revert #2396 which I should not have merged!
The result now though is config_flow.py needs this re-applied...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants