Summary

This PR addresses issue #113 by adding schema validation to the Jobs.run method. The update ensures that the configuration object passed to Jobs.run is validated against a predefined schema, preventing potential misuse or typos in the configuration.

Changes Made

• Added JobRunConfigSchema:

  • Defined a schema using Match.Maybe to validate optional fields such as in, on, date, data, priority, unique, singular, and callback.
  • The schema is applied to the configuration object passed to Jobs.run.

• Updated Jobs.run Method:

  • Added a validation step to check the configuration object against JobRunConfigSchema.
  • Ensured that the method functions correctly even if no configuration object is provided.

• Test Suite Updates:

  • Added new test cases to cover the following scenarios:
    • Running Jobs.run with only the job name.
    • Running Jobs.run with a valid configuration object.
    • Handling of invalid configurations (e.g., typos in keys).
    • Ensuring unsupported keys are rejected.

Testing

• Ran existing tests to ensure no regressions.
• Added new tests to validate the schema and ensure that errors are raised for invalid configurations.
• Edited basic.js tests after adding configSchemaValidation tests.
• Verified that all tests pass successfully.

Issue Link

Resolves #113.

Additional Notes

• This update is based on harryadel:async-migration branch, it needs to be first merged onto master.
• This update maintains backward compatibility, as the configuration object remains optional. If no configuration is provided, Jobs.run will continue to function as expected.
• The test coverage has been improved to cover potential edge cases related to configuration validation.

Please review the changes and provide any feedback. Thank you!