cuappdev / cuappdev/pear-django-backend

Modify populate logic to allow groups/interests to be updated

Open
#56 0 comments 0 reactions 1 assignee Claimed by @noah-solomon View on GitHub
bug
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

As of right now, if any of the `assets` files are updated (i.e. if the subtitle changes for an interest or if the image changes for a club), the populate endpoint will create a new object rather than updating the existing one.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.