Currently flobot can be run local via the npm start or better heroku local commands. However both methods will reset the lastQueryDate which could lead to new survey entries being lost. This issue will be resolved when a method is created to test flobot without having production side effects.
This could include creating a test TypeForm survey (with the same format as the production version) where new entries can be created and a means to read, set, and save a lastQueryDate.
Currently flobot can be run local via the
npm startor betterheroku localcommands. However both methods will reset thelastQueryDatewhich could lead to new survey entries being lost. This issue will be resolved when a method is created to test flobot without having production side effects.This could include creating a test TypeForm survey (with the same format as the production version) where new entries can be created and a means to read, set, and save a
lastQueryDate.