tanmayrajani / cinephi1e

A Messenger chatbot that suggests movies, provides plot summary.. things like that

Hi there 👋

cinephi1e's Issues

Message sequence not in order for #plot

In case of a long (3-4 sentence) summary of given movie, the sentences received by the end user are often not in order hence it doesn't make much sense.

Send messages sequentially using promises or async or something similar to achieve this. Recommended is promises which is inherent and not requiring any libraries.

Movie trailers

Possible tags:

sneakpeek

trailer

Can use Google search or YouTube search API for getting the trailer link?

Movie reviews

reviews

#guessthemovie

A mini game that lets users guess which movie a said quote is from.
Users start the game with "#guessthemovie" and the bot sends a quote. The bot answers yes/no until the users guesses the movie name correctly. Can allow for phonetic deviations and missing words like 'the', but not major deviations from the name.

Help if mis-typed

Help if mis-typed

Users either forget the hash or type something gibberish. If hash is forgotten, then tell them "you mean #meta ?" (if "meta" is typed)

And if gibberish is typed, the current message shall be given as well as a help GIF shall also be sent

Add release date

Users might be interested in the release date of a movie. We can show it in the plot summary or possibly add a #meta tag to show other metadata too.

Fails when there are unescaped parenthesis "(500) days of summer (2009)"

It stops responding after getting this error. Following is the error log:

2017-04-23T07:04:07.425346+00:00 app[web.1]: Msg text: "(500) days of summer (2009)"
2017-04-23T06:57:47.234810+00:00 app[web.1]: SyntaxError: Invalid regular expression: /^(/: Unterminated group
2017-04-23T06:57:47.234812+00:00 app[web.1]:     at new RegExp (native)
2017-04-23T06:57:47.234813+00:00 app[web.1]:     at SoundEx.process (/app/node_modules/natural/lib/natural/phonetics/sou
ndex.js:72:39)
2017-04-23T06:57:47.234813+00:00 app[web.1]:     at compare (/app/node_modules/natural/lib/natural/phonetics/phonetic.js
:29:21)
2017-04-23T06:57:47.234814+00:00 app[web.1]:     at changeTextNatural (/app/index.js:135:58)
2017-04-23T06:57:47.234814+00:00 app[web.1]:     at /app/index.js:431:41
2017-04-23T06:57:47.234815+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/rout
er/layer.js:95:5)
2017-04-23T06:57:47.234816+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2017-04-23T06:57:47.234816+00:00 app[web.1]:     at Route.dispatch (/app/node_modules/express/lib/router/route.js:112:3)

2017-04-23T06:57:47.234817+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/rout
er/layer.js:95:5)
2017-04-23T06:57:47.234818+00:00 app[web.1]:     at /app/node_modules/express/lib/router/index.js:281:22

Movie ratings

ratings

Or clubbed with #meta

Handle exceptions due to bad input gracefully

Currently the code is written in such a way that any bad input that causes a regex error or any other exception will bubble up and the server will go down.
A catch-all block should be added to the request handler to log an error and reply with an appropriate message. This will avoid server crashes due to bad input and present a better user experience in general.