Yaron Schneider
Yaron Schneider
> I prefer to keep it separate from the state store. Maybe we can create an adapter to reuse state store codes, just like: > > * [[Proposal] Create an...
Needs cherry pick for 1.15
Linter @famarting
@philliphoff can you please check why e2e tests are failing? It'd be great to get this merged
Looks like we need to error instead of warn if we fail to load components due to an error. This would be somewhat consistent with what Dapr does when initializing...
> This is especially annoying that the components are scoped to their individual apps and they still cause this error. For example component01 is scoped to app01, but an error...
Good idea, but since Distributed Scheduler also brings a new API that is completely decoupled from actor reminders and workflows, it might be good to add the cron support there...
> @yaron2 I'm going to have to see how that documentation evolves, because I thoroughly don't follow what precisely a job _is_ from it. https://v1-14.docs.dapr.io/developing-applications/building-blocks/jobs/jobs-overview/
Since the scheduler service is the subsystem for both reminders and the jobs API it would be very easy to add cron support for both and keep the API consistent