jtibble/pabtc

Tournament-Tracking Engine for Planetary Annihilation, featuring Bitcoin

pabtc's Issues

REST services should return hrefs for resource locations

Rest services should return an href property so callers can fetch the resource directly, especially on resource creation.

http://youtu.be/5WXYw4J4QOU

Redirect to invoice screen when payment is required

Instruct user that creating tournament or registering for buy-in tournament will redirect to an invoice-page where they must pay, and then implement the redirect.

REST service: Get Users

Returns list of users to the caller

REST service: Create Tournament

Things to include:

• Name
• Host(s)
• Website/URL
• Start Date/Time
• End Date/Time
• Buy-In
• Number of Participants
• Player List

Basic API-key Flow

1. User Created
2. User calls /users/[id]/createAPIKey
3. Service creates secret UUID and stores it in DB, and returns to user. This key can only be generated ONCE. Repeat attempts to generate API key will fail. Warn the user appropriately.
4. User sends API key in header for requests that require permissions. (SSL will encrypt headers later)
5. Service checks key against db for protected services and allows/disallows the action.

Registration Tests

Need tests for following scenarios:

1. Tournament does not exist
2. Tournament has no room
3. Tournament has incorrect status
4. User is already registered to tournament

Users should not be able to register without valid bitcoin address

Provide input validation when users are registering to check that they have provided a valid bitcoin address.

GET /api/v0/users times out when no users are in db

GET users fails when db has no users
expected: empty array

REST service: Get User Details

Returns details about a user including tournaments entered, won, lost, date registered, etc

REST service: Create User

Creates User, requiring:

• Username
• Password
• Timezone
• Payout Address

Returns API key for calling non-public REST services as that user

Registering Users to Tournament removes existing registered users

Create Mod UI

Create simple PA PAMM-listed Mod to call REST services and retrieve/display data.

REST service: Get Tournaments

Returns list of tournaments and all relevant details:

• Name
• Participants
• Status (Open for Registration, Registration Closed, Underway, Paying Out, Completed)
• Fee
• Start/End Date
• URL
• Host
• Format

Refactor MongoDB "Registration" Collections

Change "Registrations" collection into TournamentUsers collection. When a user registers for a tournament, create a record in that collection that will store the status of the registration, as well as the mapping from tournament-to-user and vice-versa.

Use this collection to do a parallel-search when fetching tournaments and users.

Integrate REST services with BitPay API

Use https://github.com/bitpay/node-bitpay-client to connect to BitPay API and create invoices.

Track invoice status and advance TournamentUser registrations when invoice is paid.

Schemas: Users, Tournaments, Payments, BTC interactions

Create JSON descriptions of schema objects and fill database with them when app initializes in debug mode for testing services.

Console error on registration

Registering tries to call undefined function. Fix it.

GET /api/v0/tournaments fails with 404 when db has no tournaments

Bug: tournaments service returns 404 when db does not contain any tournaments.

Expected: return empty array

Deploy to pa-btc.com

REST service: Register User to Tournament

Begins process of joining a user to a tournament.

If the tournament is free-to-join, and there are open spaces, then the user is added.

If the tournament is full, the registration is rejected

If the tournament has a buy-in, then it starts the buy-in flow

REST service: Edit User

Validate caller too

Create Admin UI

Create framework, structure, first iteration on Admin UI

Create API Documentation

Create API-docs alongside the Admin UI

Create Public-Facing Information Screens

Using REST services, create UI screens to give info about the currently-created tournaments and users, past, present, and future.

Change-Status REST service allows for illegal state transitions

Tournament should not be able to have its state changed if prize payment is expected but not yet received

Closing paid tournament should pay the winner

GET /api/v0/users returns object for only 1 user in db

Bug: returns object, not array with one object
Expected: [ {user} ]

REST service: Conclude Tournament

Create service to be called from Admin UI to 'end' a tournament, paying out the winners if necessary.

Create MongoDB instance and store data from services

Begin by storing domain objects and retrieving them through REST services.