Steven Giesel
Steven Giesel
@egil as this is only a doc update, I'd merge that into `v2`
That was to some extent on purpose: The reason is that we wanted to be in line with the Minimal API: ```csharp app.MapGet("/", () => ...); ``` I am fine...
Well simply put, we could forward it towards OrchestrationId: ```csharp public Guid CorrelationId => OrchestrationId ``` I like to keep CorrelationId as it is better suited as a name. Web...
Absolutely - still we could toy with different names. For example TraceId might be better suited.
Very good point! > It's allowed to call AddNCronJob() multiple times. I would also keep it that way, it may seem redundant, but for folks that split their logic, this...
> What advantage is there to requiring the end user to add more boilerplate code like `.UseNCronJob()`? That we can make certain checks we can't do in `AddNCronJob.` That includes...
There are not there - hence the ticket.
Sure, we could do this. I know at least one user who reported that he used multiple `AddNCronJob` calls in different places. (See #138) Analyzers could be one way of...
> f the order of the registrations of NCronJob is determined by where the `UseNCronJob()` appears then features like RunAtStartup won't really "run at startup.". It'll run based on where...
Fair enough - the naming might be wrong given that you can put it somewhere or never call UseNCronJob (we could throw an exception in that instance). Today, as you...