Open marcioos opened 7 years ago
Since we need to do parsing by hand in the telegram update (text message), I suggest to separate the commands in /search <name>
and /propose <bgg_id>
.
WDYT?
I think it would be nice if the user could just /propose <whatever>
and the bot figures out what to do (prompt the user with possible matches or post the proposal message directly). I think we can achieve that with a single propose
endpoint that routes to the proper logic based on the parameter type: if it is an integer, treat it is as a bgg_id
, otherwise as a game name.
WDYT? Too naive?
I like the approach suggested originally, being only one entrypoint that acts accordingly. Maybe it is a bit too naive, but I have the impression that the usage will be simpler this way.
Ok. =)
Let's go for it!! o/
On Mon, May 22, 2017 at 10:30 PM Fabricio Leotti notifications@github.com wrote:
I like the approach suggested originally, being only one entrypoint that acts accordingly. Maybe it is a bit too naive, but I have the impression that the usage will be simpler this way.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcioos/bg-club-bot/issues/1#issuecomment-303211555, or mute the thread https://github.com/notifications/unsubscribe-auth/AABaZfkDwjJMZe-cbmQWhjKrHHoE_4BKks5r8fBQgaJpZM4Nie8Q .
--
Thiago Rodrigues Colucci Mobile: +46 076 526 0020
The free-text propose endpoint should be hooked to the
/propose name of the game
bot command. It will search bgg using thebgg-axios
search function and do either of the following actions based on the search output:bgg-id propose
does.