Catch User Errors

[Rob Donnelly]

In general, catch bad usage and provide good error messages. Some work has already been done to validate DSL methods' inputs. This issue is an attempt to identify all areas where we can check, catch, and report bad usage.

• job command
  • predecessor not found (0b95522)
  • requires block (cc55954)
  • requires execute command (a2346fb)
• job.execute command
  • requires String or block (101e8eb)
  • requires String or block, not both (101e8eb)
  • requires String if not null (101e8eb)
• job.repeat command
  • requires Integer (c1a54d4)
  • requires positive Integer (c1a54d4)
• import command
  • require string prefix (6a0a017)
  • require non-empty prefix (6a0a017)
  • require file exists (6a0a017)
• check job graph has no cycles (Check implemented indirectly as job/'predecessor not found' check. User is unable to create cycles since jobs cannot be referenced until defined.)
• job description syntax errors (3c02885)
• jobrnr command
  • require valid file argument (#34)
  • require valid options (#36)

[Rob Donnelly]

All items completed.