On my team, we've been implementing error handling in agenda jobs in one of two ways:

1. Catch the error, call job.fail(err); job.save(), return
2. Throw the error

After looking at the job processing code for the run method, I confirmed the two approaches were equivalent.

While

Some tasks are self-explanatory if you looked at their script and need no description. I also think knowing what script the task actually runs can be helpful context if only reading from the help dialog and not the maidfile itself.

For instance, I have a clean task that just runs rm -rf build/. If the help dialog outputted this, I wouldn't need to add a description, but since it doesn't I

• VS Code Version: 1.38.1
• OS Version: Windows 10 v 1903 (build 18362.356)
• Code Runner Version: 0.9.14
• Nim version: 1.0.0 (and Nimble v0.11.0)

Describe the bug
I saw this while working throug

From twitter:
https://twitter.com/bbrannic/status/1077892960426041344

The following repo has a good reporting solution which expects the test-run results in JSON format
https://github.com/damianszczepanik/cucumber-reporting

Zerocode already produces test-run results in JSON format.
Some subset of data from this is used for CSV reporting and some for HTML reporting.

Currently it uses _e

• Constant vs Variable scopes inlining behavior
• Escaping with %%var%%`
• Special variables like %%NakeScriptDirectory%%`
• Automatic quoting in commands

If there are two activities on the same day, the formatting breaks.

Expected behavior:

1. Only show one activity if there are two on the same day
2. Default to planned activity if there is one
3. Otherwise, use the most recent activity by start_at