HangfireIO / HangfireIO/Hangfire
Best Practices: Is there a recommended pattern for creating Job classes?
Open
t: question
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Since you are familiar w/ SideKiq, typically you might create a Worker class with a perform method that basically takes the params that the class might need, the inherited methods to enqueue, schedule can then be called.
ex: https://github.com/mperham/sidekiq/wiki/Getting-Started
Any suggestions?
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the Hangfire job-class guidance and the linked Sidekiq Getting Started pattern, then determine whether a concrete documentation change or example is expected; done would require an agreed recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100