As the Challonge API (v.1) only exposes users as players in a tournament, let's only search for users in a given Challonge org's tournaments.

For this we will need DB storage.

Allow sign-up to tournament in the following ways:

• Action button per tournament in tournament list (/challonge tournaments)
• /challonge signup <tournament URL> command Skipped
• /challonge signup command with an action menu to choose from

Dependent on #4.

Hello my name is Mattias and I run a popular hockey tournament at Trimma AB. I'm coding stuff against the Challonge API and am interested in the scope and ambitions of this project!??!

;)

Move above IF-statement and remove one

Select your tournament nick as part of sign-up., preferably selecting among previously used nicks.

Dependent on #12.

https://ramdajs.com/docs/#indexBy

• Run tests on every PR.
• Run ESLint on every PR.
• Deploy on every commit to master

https://github.com/sebgrohn/challonge-bot/blob/8039a625002c8dc5aaec6de9c1f1462c299642aa/src/bot.js#L91

Like in slackbot /remind list responses.

List open tournaments for Challonge organization.

Not a strict MVP req, but helped me in learning Claudia.

map |> unnest is flatMap right?
https://ramdajs.com/docs/#chain

Deploy via Travis CI on every commit to master.

Things we need for this:

• Challenge user (for API key)
• Challenge org: https://tournie.challonge.com/
• Dynamic SimpleDB "domain" name (depends on #13) or a separate AWS account.
• Slack workspace(s) with configured Slack app

Split from #21.

Make sure to follow Slack's style guide for slash commands.

Details:

• /challonge login -> /challonge connect
• /challonge logout -> /challonge disconnect?
• Use delayed responses for all messages that query ChallongeAPI? Might avoid the dreaded timeout errors from Slack.

Report score on one of user's open match in a tournament for Challonge organization.

Depends on #4.

List open matches for a given user in all tournaments for Challonge organization:

• opponent (Slack user + tournament display name),
• time of “opening”,
• etc.

Depends on #4.

https://ramdajs.com/docs/#evolve

https://ramdajs.com/docs/#project

I found a Node.js Challonge API wrapper: Tidwell/node-challonge. It might make sense to use that instead of calling the API ourselves:

Pros:

• Automatic snake_case to camelCase conversion of request params and responses.
• Automatic date-time string to Date object conversion?

Challonge Bot is basically just a description. Could we have something more fun, plz?

Use delayed responses for all messages that query ChallongeAPI? Might avoid the dreaded timeout errors from Slack.

Split from #16.

To upgrade old functions to the new runtime, execute claudia update --runtime nodejs12.x.

Claudia 5.10 release notes

https://ramdajs.com/docs/#identity

Add code support for different config per environment (development / production) and add configuration info about deploying to different environments.

• Deploy different versions for development, testing and production
• Setting up package.json for easy deployment

Using Jest. It is probably helpful to create a mock Challonge API as well as intercept Slack messages and responses to have a baseline for what to expect.

• Design testable Lambda functions

• I want to avoid having to manually set up SimpleDB permissions in AWS Console.
• Also, SimpleDB domain(s) should be created via aws command or similar instead of in code.

• Checklist for using external services
• Serverless API with DynamoDB, using AWS Lambda