Create standardized Abstract Action, Validator, and Handler

[juni-b-queer]

The base Abstract class for all actions should be AbstractAction, AbstractMessageAction will extend AbstractAction

The base Abstract class for all validators should be AbstractValidator, AbstractMessageValidator will extend AbstractValidator

The base Abstract class for all handlers should be AbstractHandler, AbstractMessageHandler will extend AbstractHandler

This will then allow us to make Generic actions, validators, and handlers that don't rely on a message.

We can also make actions, validators, and handlers for each subscription type AbstractInterval{Action|Validator|Handler} while still maintaining the Abstract structure.

Abstract{Validator|Action|Handler}.handle should only accept a HandlerAgent

High level Todos

• [x] Validators
  • [x] Create AbstractMessageValidator that is a copy of the existing AbstractValidator
  • [x] Update AbstractValidator to not require a message in the shouldTrigger and handle functions
• [x] Actions
  • [x] Create new AbstractAction that doesn't require a message in handle, make AbstractMessageAction extend it
• [x] Handlers
  • [x] Create new AbstractHandler where handle doesn't require a message. AbstractMessageHandler should extend it

[juni-b-queer]

:tada: This issue has been resolved in version 2.0.0-beta.2 :tada:

The release is available on:

• npm package (@beta dist-tag)
• v2.0.0-beta.2
• GitHub release

Your semantic-release bot :package::rocket: