Add discussion and discussion_entry models to backend

[anthonyshibitov]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

movement_id and vote_id are currently not implemented, denoted by comments.

Let me know if there's any issues with this. This is my first foray into backend stuff 🤠

Related issue

• Add discussion models to the backend #619

[netlify]

✅ Deploy Preview for activist-org ready!

Name	Link
🔨 Latest commit	ddfa97f
🔍 Latest deploy log	https://app.netlify.com/sites/activist-org/deploys/66146b0dcbf2600008a328cc
😎 Deploy Preview	https://deploy-preview-688--activist-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo

• The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[anthonyshibitov]

Not sure how to implement dummy models for movements and votes, hence the below backend fails:

backend/content/models.py:26: error: Cannot find model 'entities.Movement' referenced in field 'movement_id' [misc]
backend/content/models.py:29: error: Cannot find model 'events.Vote' referenced in field 'vote_id' [misc]

[andrewtavis]

For now we'll just comment them out, @anthonyshibitov :) Thanks!

[andrewtavis]

Ok, soooo, this is quite weird. @to-sta, the errors that are coming up now for the backend are what I was seeing in PyLint that we said were false positives 🤔 Can you take a look?

[to-sta]

Ok, soooo, this is quite weird. @to-sta, the errors that are coming up now for the backend are what I was seeing in PyLint that we said were false positives 🤔 Can you take a look?

Hi @andrewtavis, maybe its related but the backend workflow discovered static type issues and unsorted imports. Does pylint cover those?

I saw that inheritance was missing for the viewsets, that solves most of the static type issues.

class DiscussionViewSet:
     ...

class DiscussionViewSet(viewsets.ModelViewSet[Discussion]):
    ....

I think the rest of the static type issues are related to the use of model fields that don't exist.

[to-sta]

I fixed the mypy, linting and formatting issues. @andrewtavis and I renamed the user_id field from DicussionEntry to created_by.

[andrewtavis]

Final commit on my end was mostly keeping the changes from the branch here and organizing things. Thanks so much for this, @anthonyshibitov! Always a pleasure, and again apologies that this took so long. Also thanks for the fixes, @to-sta! 😊