-
-
Notifications
You must be signed in to change notification settings - Fork 487
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/v1/ for Case Contacts (iOS App) #3942
Comments
When this is almost done we'll probably need to talk to sean about a r4g ios publishing account. https://developer.apple.com/support/membership-fee-waiver/ |
Is this still a priority? |
@dpaola2 A dev team is working on this. Don't worry about it |
OK. Should I close? (Which dev team?) |
No don't close it. It's codethechange |
This issue has been inactive for 245 hours (10.21 days) and will be unassigned after 115 more hours (4.79 days). If you have questions, please If you are still working on this, comment here to tell the bot to give you more time |
this project is still being worked on. Don't close yet! |
Maybe if I slap the epic tag on it the bot will ignore it |
This issue has been inactive for 531 hours (22.13 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project. |
This issue has been inactive for 843 hours (35.13 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project. |
This issue has been inactive for 1275 hours (53.13 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project. |
This issue has been open without changes for a long time! What's up? |
This issue has been inactive for 11355 hours (473.13 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project. |
What type(s) of user does this feature affect?
Description
A volunteer needs to be able to use the app to save a case contact.
Approach
Authentication
Case Contact
For Additional Expenses (they are nested under Case Contacts)
Requirements for /api/v1/
Secure Authentication (token based)
/api/v1/users/sign_in
Foundation: iOS app can authenticate on sign_in endpoint Initial API Structure + Auth Route #4976, and below
Token Refreshing: iOS app generates new access tokens when refresh token is still valid
/api/v1/users/refresh_token
Token Revoking: iOS app can Sign-Out users on sign_out endpoint
/api/v1/users/sign_out
Session tokens default to expire 1 month after creation, requiring re-login
Endpoint /api/v1/users/sign_out revokes access token and refresh token on request #6222 Volunteers Sign-Out endpoint invalidates current session/access token and refresh token when requested
Casa Case Endpoint for Signed-In Users
/api/v1/casa_cases
Milestone 1
Milestone 2a
Milestone 2b
Milestone 2c (expand case contact data)
casa_case_contact_types
to show which contact types are available to be selected for the case contactcase_contact_contact_types
to show contact types have been selected on the case contactcontact_topic_answers
to show sections of notes for the case contactMilestone 3a
Milestone 3b
We have jBuilder installed. It can help you if your json response is complicated. You can also use it to convert a rails object into json easily like this
Questions? Join Slack!
We highly recommend that you join us in slack https://rubyforgood.herokuapp.com/ #casa channel to ask questions quickly and hear about office hours (currently Tuesday 6-8pm Pacific), stakeholder news, and upcoming new issues.
The text was updated successfully, but these errors were encountered: