Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Listen for new RSVPs in ActionKit [3] #1

Open
aguestuser opened this issue Mar 19, 2018 · 0 comments
Open

Listen for new RSVPs in ActionKit [3] #1

aguestuser opened this issue Mar 19, 2018 · 0 comments
Labels
Milestone

Comments

@aguestuser
Copy link
Contributor

aguestuser commented Mar 19, 2018

Acceptance Criteria

GIVEN a running server with an API key for a client's ActionKit account

  • THEN EVERY HOUR, the server will retrieve all events associated with that account and all RSVPs associated with each event
  • AND THEN the server will store a record of any new events or RSVPs in the database (including a reference to the Event/RSVP's id in actionkit)

Definitions

[stub]

Out of Scope

We will not listen for events in a specific campaign. Rather we will listen for all events associated with a given clients ActionKit account.

@aguestuser aguestuser added this to the ak-van-sync milestone Mar 19, 2018
@aguestuser aguestuser changed the title Listen for new events in ActionKit [3] Listen for new RSVPs in ActionKit [3] Mar 19, 2018
aguestuser added a commit that referenced this issue May 30, 2018
* add typescript & testing dependencies
* write trivial passing test

co-authored-by: vaughanj10 <[email protected]>
aguestuser added a commit that referenced this issue May 30, 2018
co-authored-by: vaughanj10 <[email protected]>
aguestuser added a commit that referenced this issue Jun 20, 2018
* given array of event/signup/person trees in ak format as
  input, produce an array of event/signup/person trees in van format

side-effects:

* update fixtures
* update types
aguestuser added a commit that referenced this issue Jun 20, 2018
side-effects:

* add phone numbers to fixtures
* provide mock responses for phone number API requests
aguestuser added a commit that referenced this issue Jun 21, 2018
* move secrets to `./config/secrets`, import them in `/config.index`
* dispatch on NODE_ENV to export config matching environment
* only read NODE_ENV in `/config/index` (ie: NOT in sequelize setup)
aguestuser added a commit that referenced this issue Jun 21, 2018
n# Date:      Wed Jun 20 20:58:30 2018 -0400
aguestuser added a commit that referenced this issue Jun 21, 2018
* move secrets to `./config/secrets`, import them in `/config.index`
* dispatch on NODE_ENV to export config matching environment
* only read NODE_ENV in `/config/index` (ie: NOT in sequelize setup)
aguestuser added a commit that referenced this issue Jun 21, 2018
* move secrets to `./config/secrets`, import them in `/config.index`
* dispatch on NODE_ENV to export config matching environment
* only read NODE_ENV in `/config/index` (ie: NOT in sequelize setup)
aguestuser added a commit that referenced this issue Jun 22, 2018
side-effects:

* refactor config/index for concision, allow for named imports
* add type declaration to `initDb()`
* fix db types for `models/Event`, provide return type for its factory
* extract `vanEvent` fixture with no nested attributes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant