This abstract class concerns itself with representing a method of matching a specific statement
and translating it to a form that Spanner understands. The user should call is() to determine
whether it matches before trying to translate.
Dynamic command allows the specification of user generated commands. Via the generation of a JSON
file, a user may determine input and output parameters as well as matchers counts, which will be
used to dynamically generate a matcher for a specific run.
Fallthrough Command which should match most meta-commands. We are expected to run this last in
the matching logic to present the user with better error statements.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-26 UTC."],[],[]]