velet5 / ufag Goto Github PK

Now it's just a bunch of if-else statements.

At least methods should have meaningful names.

One example was found so far: "? сутра" (russian)
The first correction is "сутра", which is the same word that was in the original request.
Figure out - why that is happening.

My first assumpltion is that although question-mark prefix implies definition of the word - we are looking for corrections in the "translations" dictionary.

For example: /ask command requires text argument, but if argument is not provided then parser considers this an unknown command.

Instead parser should return textual error message which can be sent to user.

Add /unsubscribe and /subscribe command to allow users manage their subscription

rewrite /help text - with examples

Problem: Now word correction suggestions are in plain text. User has to type the whole word all over again.

To do: Turn every suggestion into a button. Button tap should be treated as regular translation request.

Pretty-print oxford articles.
Analyze current "processing error" messages.

Release /ox functionality.

Problem: bot owner's reply to /ask isn't recognized. It's being treated like translation request.

Use LiquibaseRunner main class

For example: if for some word like "asfsadf" bot has returned "nothing is found" or "maybe you meant: asdf" - don't try to remember these queries, just ignore them

Now 404 response from oxford dictionary results in "Processing error".
Should result in "definition not found".

Make it pure functional, replace var, @volatile, Future and Promise with Ref, Deferred and IO

all parameters should be interfaces (for future tests)

this should be rendered as "see trainspotter", now it's just an empty line

do minimal word processing:

• lowercase
• trim
• maybe strip special symbols

/ask itself is working ok.

But owner's reply to it does nothing.
Seems that storing original message id is broken.

Show information about in which context a definition is used (e.g. - military, outdated, art).

It appears docker ps --filter 'ancestor=velet5/ufag' doesn't always work as expected.
So, old container stays there and new one cannot start, because port 8080 is occupied by the old contatiner.

Rewrite services with cats.IO instead of Future, use tagless final notation F[_]

If user's query hasn't resulted in an article - suggest spelling corrections for such query.

Implement this via https://developers.lingvolive.com/ru-ru/Help/Api/GET-api-v1-Suggests_text_srcLang_dstLang

Replace every "println" statement with logging through logback

Remove handlers of "/ru" and "/ox" (don't forget to remove them via BotFather)

see src/main/resources/migrations

Add /news command available for owner only to deliver information about new features to users.