Skip to content

feat: add Poll component to standardize polling behavior #1556

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

Draft
wants to merge 4 commits into
base: 5.x
Choose a base branch
from

Conversation

mathiasgrimm
Copy link

  • Centralizes interval-based logic in reusable Vue component
  • Reduces polling frequency to hourly when window not visible
  • Improves code maintainability and reduces redundancy

This significantly reduces the bandwidth usage when the browser tab is not active.

- Centralizes interval-based logic in reusable Vue component
- Reduces polling frequency to hourly when window not visible
- Improves code maintainability and reduces redundancy
- Centralizes interval-based logic in reusable Vue component
- Reduces polling frequency to hourly when window not visible
- Improves code maintainability and reduces redundancy
- Centralizes interval-based logic in reusable Vue component
- Reduces polling frequency to hourly when window not visible
- Improves code maintainability and reduces redundancy
- Centralizes interval-based logic in reusable Vue component
- Reduces polling frequency to hourly when window not visible
- Improves code maintainability and reduces redundancy
@@ -0,0 +1,111 @@
<script type="text/ecmascript-6">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rewrite this as a plain javascript function and not a vue component. Now every polling function needs an associated html element in the DOM.

@taylorotwell taylorotwell marked this pull request as draft May 27, 2025 22:29
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