When configuring Quantum with unnamed jobs (e.g. config :your_app, YourApp.Scheduler, jobs: [{"@daily", {Backup, :backup, []}}]), then the name is a Reference, which can't be printed using #{name} as was previously done, so if there is a problem with the job (e.g. the function does not exist), this leads to an error that stops the application from starting rather than just a warning in the log. This PR fixes this by adding a function job_name_to_string/1 that can handle References.
When configuring Quantum with unnamed jobs (e.g.
config :your_app, YourApp.Scheduler, jobs: [{"@daily", {Backup, :backup, []}}]
), then thename
is a Reference, which can't be printed using#{name}
as was previously done, so if there is a problem with the job (e.g. the function does not exist), this leads to an error that stops the application from starting rather than just a warning in the log. This PR fixes this by adding a functionjob_name_to_string/1
that can handle References.