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

Component Based Queue #166

Closed
dskvr opened this issue Jan 9, 2023 · 0 comments · Fixed by #171
Closed

Component Based Queue #166

dskvr opened this issue Jan 9, 2023 · 0 comments · Fixed by #171
Labels
asap enhancement New feature or request

Comments

@dskvr
Copy link
Collaborator

dskvr commented Jan 9, 2023

Is your feature request related to a problem? Please describe.
Identified an efficient pattern for running tasks that doesn't require webworkers or extraneous work in queue logic. Piggybacks off existing task management.

Describe the solution you'd like

  • Component conditionals ensure only one task is ran at a time.
  • Each task uses the tasks store for getting and setting task status
  • When a task completes by signaling tasks store the component will unload, and another task component will take over.

Describe alternatives you've considered

  • store driven queue
  • other existing queue solutions
@dskvr dskvr added enhancement New feature or request asap labels Jan 9, 2023
@dskvr dskvr closed this as completed in #171 Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
asap enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant