codebuddies / backend

CodeBuddies back-end
https://codebuddies.org
GNU General Public License v3.0
20 stars 25 forks source link

Issue 160 hangouts endpoint first pass #193

Closed BethanyG closed 2 years ago

BethanyG commented 4 years ago

What type of PR is this? (check all applicable)

working branch: issue-160-hangouts-endpoint Note: Because this code has been branched from the work in dj-rest-auth, the commits for PR #187 can also be seen in this PR.

Context

"Rough Draft" of Hangouts endpoint. Includes app.py, models.py, and admin.py. See issue #160 for more detail and the inter-related issues for tracking. See FE discussions https://github.com/codebuddies/frontend/discussions/137 & https://github.com/codebuddies/frontend/discussions/139 for additional discussion.

Other Related Tickets & Documents

161, #163, #164, #167

Implementation Details

What was your thought process as you changed the code? What does someone need to consider in reviewing it?

I left notes and questions under the related issues. Model and JSON are far from finalized. Additionally, this build has a somewhat "broken" admin interface -- inlines are not working there yet.

Added a hangouts app Added hangout, hangoutresponses and hangoutsessions tables Added a many-to-many for resources to hangout and to hangoutsessions Added a many-to-many for users to hangout, hangoutsessions, and hangoutresponses Started to add the endpoint to the admin, but encountered some issues.

New Libraries/Dependancies Introduced (Fill out as needed)

This requires a re-build and db migrations for the new tables.

Any new migration files added?

Did you add tests?

Code added or changed without test coverage or good reason for exemption won't be approved.

Did you add documentation?

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

BethanyG commented 3 years ago

Still open.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

BethanyG commented 3 years ago

Keeping this open, as I hope to get to it soonish.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

BethanyG commented 3 years ago

Still open.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.