code-corps-api
code-corps-api copied to clipboard
code-corps
Elixir/Phoenix API for Code Corps.
# Problem We're moving away from using `ja_resource` and `canary` through #864 This makes controllers and authorization policies much more explicit and easier to follow. However, segment tracking still relies...
# Problem EDIT: See the comment below. We want to have a place for a `Project` to be explicitly approved by an admin.
# Problem Right now if there are validation errors due to timestamps being off in GitHub syncing, it appears we're seeing `validating_tasks` or `validating_comments` errors. What we should do instead...
# Problem #749 deals with upgrading to phoenix 1.3 However, part of that upgrade is the encouragement to switch from a flat layer of models/schemas into a concept of bounded...
# Problem We do not currently have a way to easily differentiate donors among all project/organization contributors. We can technically do so by inferring through subscriptions, but it's not straightforward....
We could do the following 3 items to further reduce boilerplate in controllers. However, while boilerplate is reduced, all 3 of these actions also hide behavior which we may not...
# Problem #1080 added a unique index to the `github_repos` schema. #1081 also changes behavior when syncing github repos to match by `github_id` The model for a `GithubRepo`, however, looks...
# Problem Looking at these two fields, it really seems they serve a singular purpose. ```Elixir # A project is created `approved: false, approval_requested: false` # User submits project for...
Right now, we have policies and actions in place on our API which would allow promoting and demoting project members by other project members. We do not, however, have any...
We added an `approved` column to projects and organizations almost a year ago. I'm not sure if we had the organization invite system in mind when adding it. The way...