code-corps-api
code-corps-api copied to clipboard
code-corps
Elixir/Phoenix API for Code Corps.
# Problem Right now when we send query params to the API, we are not filtering/sorting correctly. We'll need to decide if we want to tack another library on, write...
# Problem Right now, our connect event handlers are being called with `Stripe.Event` as their first argument, but most of the other factors in how their being called are kind...
# Problem We introduced #1203 to solve some problems with GitHub's second-level timestamps. We really need to consider whether this is generally enough, or if there are any edge cases...
# Problem We had an error earlier fetching an issue with event ID `e99b7a10-cbd6-11e7-9ebc-4752129e3313` at `11/17/2017 12:35:56`. The error data does not get passed along (we only log a `%{}`)...
# Problem All our `Github-x` model creation should be done as a find or create by using the `github_id`. Right now, the assumption is that this is the first insert...
# Problem Our new sync process revealed some issues caused in our use of `EctoOrdered` when there are a large number of writes. At the kind of scale we need...
# Problem When a `conversation` record is created/updated, we need to update the `open_conversations_count` and `closed _conversations_count` counter cache columns on the `projects` table. - [ ] Add `project_id` to...
# Problem In #1332, and even before that, `CodeCorps.Emails.Transmissions.Receipt.build` is wrapped into a `with` statement with multiple points of failure. The event handler code which sends this email also wrapps...
# Problem #1306 added a name fallback to the Receipt email. Other emails might benefit from this as well, and once #1332 is in, we can make use of recipient-based...
# Problem From #1332 Right now, a ReplyToEmail is send once for each participant in the conversation. Instead, we should create a transmission for all the participants. We can make...