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

Feature Request: Enhance Job and Queue Configuration with Array Tags #30

Open
SaliBhdr opened this issue Feb 12, 2024 · 0 comments
Open

Comments

@SaliBhdr
Copy link

I am reaching out to suggest an enhancement for the operations jobs and queue system, which presently relies on defining jobs as a string property. Transitioning to defining tags as an array could significantly improve the segregation of queues. Although the current system is flexible and efficient in managing tasks, I see an opportunity for enhancement.

Feature Proposal:

I propose the introduction of method-like tags that return an array of strings, similar to how jobs are handled in Laravel. This improvement would offer a more structured and intuitive approach to managing jobs and queues within Laravel applications. By implementing method tags, developers would achieve clearer insights into job responsibilities and invocation patterns, which in turn would enhance code readability and maintainability.

Benefits:

  • Enhanced Readability: Utilizing array tags provides a more descriptive method for outlining each job's purpose, thereby simplifying the understanding of the codebase.
  • Improved Maintainability: Array tagging facilitates easier updates and maintenance of job definitions by offering a clear view of the job's functionality.
  • Increased Flexibility: This feature would enable developers to handle their queues and jobs in a more refined and adaptable way, easily adjusting to complex workflows.

I am convinced that incorporating this feature would significantly benefit the package, empowering developers to create more robust and efficient applications. I am keen to hear your views on this proposal and to discuss any potential considerations for its implementation.

Thank you for taking the time to consider my suggestion. I look forward to your feedback.

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

No branches or pull requests

1 participant