HangfireIO / HangfireIO/Hangfire
AutomaticRetryAttribute work only on interface
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
I have jobs defined as interfaces in one assembly and implementation in another. My interface assembly can't use Hangfire lib dependency and I want to use AutomaticRetryAttribute on every job with different values. Job schedule and registering is done with interfaces. Is there a way to use AutomaticRetryAttribute on implementation classes?
If not, would you consider as good improvement?
I think if you have job business logic in implementation class, why not use job execution control logic also here.
Contributor guide
Research direction
Start by examining how AutomaticRetryAttribute is applied when jobs are scheduled and registered through interfaces, then compare that with the implementation classes in the separate assembly. Determine whether implementation-level attributes can be supported without the interface assembly referencing Hangfire, and define the expected precedence and behavior for different retry values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100