-
Notifications
You must be signed in to change notification settings - Fork 61
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
Api resource types #84
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! I think we're close to the point where we need to backfill test coverage and start requiring it.
@@ -0,0 +1,9 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Was this intended to be committed? If so perhaps it was meant for a test or docs directory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a file explaining how to exercise the API with curl commands. These two json files are sample data supporting those curl commands.
@@ -0,0 +1,3 @@ | |||
{ | |||
"goal": 2000.00 | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: was this meant to be committed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as a above.
I approved but we've also slid in a number of decisions like REST and PATCH method without decision records. Flagging that as necessary but I think the AI is to identify the decisions and file those as new issues. |
Test coverage is needed, as are documentation of decisions. One such decision is the behavior of PATCH and DELETE relative to etags. |
* Added most of campaigns resource * All operations for campaigns and approvers * Causes and Donors added * Add resource types
All currently defined resource types now fully implemented. API enhancements likely are needed following up.